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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context of its own — no mention of pagination, default result limits, or filtering behavior for an endpoint that presumably returns a collection.

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 text is short but front-loads a verbatim duplicate ('GET /api/recon/issues. GET /api/recon/issues.'), which is pure waste. Removing the repetition would leave only the operation ID and the describe_operation pointer.

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 no-annotation-gap read tool with an undocumented nested 'query' parameter and no output schema, the description should describe what the endpoint returns and how to filter. The describe_operation pointer offers a partial escape hatch, but nothing else an agent needs to invoke this correctly is present.

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?

With 0% schema description coverage on two parameters (a free-form 'query' object and an empty 'params' object), the description carries the compensation burden. Its single useful contribution is routing the agent to describe_operation for native request schemas, but it explains nothing about what 'query' accepts or what 'params' is for.

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 only restates the endpoint route already present in the tool name ('GET /api/recon/issues' twice), which is a tautology rather than a natural-language statement of what the resource contains or returns. An agent learns it reads something called 'recon issues' but nothing about scope, filters, or how it differs from siblings like get_recon_issues_by_id or get_recon_deadlines.

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 statement of when to use this tool versus alternatives such as get_recon_issues_by_id or get_recon_deadlines, nor any prerequisites. The only actionable hint is 'describe_operation provides native request schemas', which is a documentation pointer rather than usage guidance.

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