A bad User Story describes a large complex system, while a good one is limited in scope. This increases predictability and limits surface area for misinterpretations or big open questions. A good User Story, though, does describe end-to-end what the customer needs to accomplish, so that the developer can internalize and understand the customer problem. This allows the developer to make good implementation decisions and use their intuition versus just “doing what they’re told.”
