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 safety is covered. The description adds nothing beyond that: no definition of what a 'recon issue' contains, no not-found/error behavior, no scoping or permission notes.

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?

Very short but not concise in any useful sense: the same sentence appears twice verbatim, followed by an opaque operation UUID. Space is spent on duplication rather than on front-loading anything informative.

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?

With no output schema, no documented parameters, and a nested free-form object, the description should explain at minimum what a recon issue is and what the response roughly contains. It supplies none of that, leaving the agent unable to predict the result of the call.

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 description coverage is 0% and there are two parameters, including a free-form nested 'query' object, so the description carries the burden and does not meet it. It never names 'id' or its constraints, nor explains what the 'query' object is for; only the raw path hint ':id' weakly maps to the required param.

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 is the title repeated verbatim twice ("GET /api/recon/issues/:id") plus an operation ID. The HTTP path does imply the resource (recon issues) and a by-id lookup, but the text adds no stated purpose and does not distinguish this from the sibling list tool get_recon_issues_54383fd24a5dec1c0d6f6b13 — it is effectively a tautology.

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?

No when-to-use, when-not-to-use, or alternative is given. The only actionable hint is that describe_operation provides native request schemas, which is a procedural pointer rather than usage guidance, and it never tells the agent to prefer this tool over the list endpoint when it has a single ID.

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