User stories (option C) are typically used in Agile methodologies to capture and describe specific features or functionality from an end user's perspective. While user stories can be part of defining the intended results, they are usually more high-level and may not contain all the detailed information needed for the development and implementation teams to plan their work effectively.

Requirements (option B), on the other hand, provide a more comprehensive and detailed description of the intended results, including functional, non-functional, and technical specifications. They are a common way to document and communicate what needs to be built, ensuring a shared understanding among all stakeholders.

So, while user stories play an important role in Agile, they may not provide the level of detail needed to define the intended results comprehensively, making requirements a better choice for this purpose.