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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description adds nothing beyond the path and an operation ID; it says nothing about what is returned or permission requirements. Repeating the path verbatim is not behavioral context.

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 first sentence is repeated verbatim, which is pure waste, and the only other content is an operation ID and a pointer to another tool. Nothing is front-loaded beyond the path itself.

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 nested-object tool with a required path parameter and no output schema, the description is far too thin: it omits what is returned, the meaning of the id, and error behavior. Annotations carry the safety profile, but the call semantics remain unexplained.

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 0%, so with 2 parameters (including a required 'id' path parameter) the description should compensate, but it never mentions the id parameter or any format constraints. The reference to describe_operation provides a possible fallback but does not document the parameter itself.

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 restates the HTTP path (GET /api/recon-docs/statements/:id), which does identify the verb and resource, but it is a tautological repetition of the title rather than an independent explanation. It gives no indication of what a 'statement' is or why one would fetch it, and it doesn't distinguish this from the sibling get_recon_docs_statements (list) tool.

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?

There is no guidance on when to use this versus the list endpoint get_recon_docs_statements or describe_operation. The only hint is that describe_operation provides native request schemas, which is a pointer to another tool, not usage criteria for this one.

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