A user story is a short description of something a user needs, written from their point of view so the team builds for a person, not a spec:
As a [kind of user], I want [a capability] so that [a benefit].
Each part does a job. As a names a real role ("returns agent", "first-time customer"), not "the user" and not "the system". I want states what they want to be able to do, not how the screen looks. So that gives the reason: it lets the team suggest a better way to deliver the benefit, and it tells the product owner what the story is worth.
A story is a placeholder for a conversation, not a full specification. The detail comes from talking it through with the team and is written down as acceptance criteria, which the next lessons cover. Card, conversation, confirmation: the story card, the talk, and the criteria that confirm it is done.
Role, capability, benefit.