As A

Also when given a template people can start treating story cards written this way as mini-requirements specs focussing on the written words rather than using stories as tools for driving a conversations. Even worse that stories that don't fit this form will be battered into shape until they do. Stories help you ask the right questions about the context and reason for the request in release and iteration planning the important part is not about the words on the card but the shared understanding developed in the team.
As a Coach I want a Story Template so that People Ask Questions

Rachel Davies, reiterating the commonly forgotten point that User Stories should encourage communication not list requirements, with an example exercise for playing with user stories.  Handy.