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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered by structured data. The description adds nothing behavioral: no indication of what a cutover report contains, whether the runId must reference a completed run, error behavior for unknown runs, or response size. The 'describe_operation' pointer is a discovery hint rather than 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 identical endpoint sentence is repeated verbatim twice, and the operation ID (646108e391f59a3eea06c16c) is already in the tool name, making both inclusions waste. No front-loaded statement of purpose in natural language; the useful content is a single trailing clause.

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 and a nested 'params'/'query' structure at 0% description coverage, the description leaves the agent without a clear picture of the response or the query parameter's purpose. For a report-generation endpoint on a specialized ASC 842 reconciliation module, this is inadequate context to invoke confidently.

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%, so the description must compensate, and it does not. The ':runId' placeholder implies the path parameter's role, but the free-form 'query' object parameter is entirely unexplained, and there is no clarification of accepted runId format or validation rules beyond the schema's minLength/maxLength.

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 raw path 'GET /api/asc842-reconciliation/runs/:runId/cutover-report' does identify a specific verb and resource (fetch the cutover report for a given reconciliation run), so the purpose is inferable. However, it is delivered as an unformatted URL rather than a stated intent, and the only differentiation from the many sibling asc842 run endpoints is the '/cutover-report' suffix buried in the path.

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 sibling tools such as get_asc842_reconciliation_runs_by_runId_d0a816fb... or the reconciliation-records endpoint. The only routing hint is that 'describe_operation provides native request schemas', which tells the agent where to get details, not when this tool is the right choice.

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