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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered structurally, but the description adds nothing beyond that: no indication of what a run record includes, whether missing IDs error or return empty, or any pagination/auth context. The duplicated route string provides zero behavioral value.

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 single substantive sentence is duplicated verbatim, which is pure waste. The meta-information (operation ID, describe_operation pointer) is front-loaded but the actual purpose is never stated, so length is not the problem — redundancy and under-specification are.

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, a nested free-form 'query' object, and 0% parameter documentation, the description would need to explain the resource and the query parameter's role. It provides none of that, leaving an agent unable to use the tool beyond guessing from the route.

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 description says nothing about the two parameters (the required 'id' path param and the free-form 'query' object). The minLength/maxLength constraints on 'id' are the only signal, and the description does not compensate for the total lack of documented semantics.

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 a verbatim restatement of the HTTP method and route ('GET /api/review/runs/:id') repeated twice, which merely echoes the tool name and title rather than explaining what a 'review run' is or what the response contains. It does not distinguish this tool from the sibling get_review_runs_by_id_stream.

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, when not to, or how it relates to siblings like get_review_runs_by_id_stream. The only actionable hint is that describe_operation exposes the native request schema, which is a pointer to another tool 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.