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 fully covered structurally. The description adds essentially nothing: no scope, no pagination, no auth requirements, no mention of what the deadline list contains or how it is ordered.

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?

It is short, but only because it is under-specified, and the first sentence is duplicated verbatim, which is pure waste. The operation ID and schema-pointer note are the only non-redundant content and are not front-loaded as guidance.

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, 0% parameter coverage, and nested free-form objects, the description must carry the burden — yet it provides no return shape, no filter semantics, and no usage context. The pointer to describe_operation is the sole mitigating element.

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 the two parameters ('query' and 'params') are untyped catch-all objects with no documented fields. The description does not name a single parameter or explain the query object, and only deflects to describe_operation for the real request schema, leaving the agent without usable parameter semantics here.

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 title/name: 'GET /api/recon/deadlines' appears twice with an operation ID appended. It does not say in natural language what a recon deadline is, what it returns, or how it differs from siblings like get_recon_issues or get_recon_docs_statements. An agent learns the HTTP path but not the meaning of the resource.

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 guidance on when to call this versus alternatives, no prerequisites, no filtering context. The only actionable hint is 'describe_operation provides native request schemas', which points to a sibling for schema discovery but is not a when-to-use rule.

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