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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description goes beyond them usefully by revealing the four possible status values and that the run id and summary only appear once processing completes, which tells the agent how to interpret an incomplete-looking response.

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?

One sentence, front-loaded with the resource and outcome; the parenthetical status list earns its place. Slightly dense phrasing ('with the run id and summary once processed') but no wasted sentences.

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, the description carries the return-value burden and does so reasonably by listing statuses plus run id and summary. It is thin only on the request_id input and on what an agent should do while status is pending, which are minor for a simple, fully-annotated read tool.

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% for the single request_id parameter, so the description is the only place semantics could be supplied — yet it never explains what request_id is, where it comes from, or its expected form. 'A target request' is the only hint and it is too vague to compensate.

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 names a specific resource (a target request) and the exact information returned (status, run id, summary), and it enumerates the four status values. It doesn't explicitly contrast with request_target, but the 'target request' scoping makes the intent clear against siblings like get_divergences or list_tools.

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?

Usage is only implied: reading 'once processed' suggests polling a request previously submitted via request_target, but the description never states when to call it or what the alternative is if no request exists. No explicit when/when-not guidance is present.

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