Get User Story

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=true, which covers the safety profile and open-world expectations. The description adds no further behavioral context—such as authentication requirements, response size implications, or side effects—so it neither enhances nor contradicts the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, focused sentence that delivers the essential purpose without any filler words, redundant details, or unnecessary context. It is optimally concise and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only get-by-id tool with 100% schema coverage and clear annotations, the description is nearly complete. It lacks a brief note on when verbosity might matter, but this is already captured in the schema, so the description adequately supports tool selection and invocation for this low-complexity tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema fully documents both parameters: id (integer) and verbosity (enum with detailed explanation of trims and defaults). The description restates that it fetches by id but adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb (Get), the resource (single user_story), and the key parameter (by id). It distinguishes this tool from siblings like user_story_list (multiple stories) and user_story_create/update/delete, so an agent can easily select it for single-record retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'by id' implies this tool is for fetching a specific user story when the id is known, but it provides no explicit guidance on when to use this instead of user_story_list or other alternatives. No exclusions or alternative tool names are mentioned, leaving usage to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.