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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds the useful state-conditional detail that result links only exist after success. It does not cover whether repeated calls are safe (notably idempotentHint=false is left unexplained) or whether failures surface in the same shape. With an output schema present, further return-value detail would be redundant, so a 3 is fair.

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 short clause with zero padding, and the highest-value facts are front-loaded. The telegraphic, semicolon-joined phrasing is terse to the point of reading as a note rather than a definition, but nothing is wasted.

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?

Annotations and an existing output schema carry much of the burden for a one-parameter read tool, so little is strictly missing. The gaps that remain, chiefly the meaning and provenance of generation_id and the lack of routing versus list_generations, keep it at minimally adequate.

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 required parameter, so generation_id is undocumented in both places. The description never says what a generation_id is or where it comes from (presumably the generate response), which is exactly the gap the description should fill at low coverage.

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?

States the resource ('a generation') and what the call surfaces (status, result links, charge), which is enough to tell it apart from list_generations, generate and get_model. It is written as a noun phrase rather than a verb, so the retrieval action is implied rather than stated, and no sibling is named explicitly.

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 when-to-use guidance: nothing says whether this is for polling after generate, for inspecting a single result, or how it differs from list_generations. The clause 'once it has succeeded' hints at polling but leaves the alternative and the pre-condition unstated.

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