get_story

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

The description describes a read-only retrieval, but annotations have destructiveHint=true, which is a direct contradiction. No additional behavioral traits are disclosed beyond the contradictory annotation, such as any side effects or permissions needed.

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 sentence that efficiently communicates the purpose and return structure. It is front-loaded and concise, but lacks a bit of structure (e.g., bullet points or separate sections). Still, no waste.

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?

Given the annotation contradiction and lack of output schema, the description does not provide enough behavioral context. It omits any mention of potential side effects or destructive actions, which are hinted at by the annotations. The tool is simple, but the contradiction makes it incomplete.

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?

Schema coverage is 100%, so the schema already documents the story_id parameter with a description. The description adds no extra meaning to the parameter, so baseline 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' and the resource 'full markdown content and metadata for a single story'. It also lists the return fields, which distinguishes it from siblings like list_stories that return multiple stories.

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 description implies usage for retrieving a single story's details but does not explicitly state when to use this tool versus alternatives like list_stories, nor when not to use it. The context of having many sibling tools makes this a gap.

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