User Stories should follow this format.
As a (role) - This can be an end user or a business proxy
I want - A description of what needs to be done
So that - the definition of the value
Acceptance criteria is then required so you know when you are done. This can be a bullets list, like you have, or context specification style (part of BDD - Business Driven Development).
The one major bit of advise I have is do not write the User Stories on your own. Creating a backlog using User Stories is a collaborative technique. Without this, you will be missing the point and main advantage of this approach. Emergent requirements and valuing customer collaboration over contract negotiation.
If you would like to know more I suggest reading Mike Cohn's User Stories Applied.