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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lowered. The description adds real value by disclosing the returned fields (prompt, model, settings, inputs), which matters since there is no output schema; it stops short of describing error behavior for a missing id.

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?

A single front-loaded sentence that names the resource first, then the returned contents, then the use case. The API-path reference is slightly technical filler but overall efficient.

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?

For a simple single-parameter read with annotations covering safety, the description supplies the return contents and use context. Missing only edge-case behavior (unknown id), which renders it nearly complete.

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?

With one parameter at 0% schema coverage, the description only implicitly maps generation_id via the GET /generation/{id} path and "one generation." A single integer id is largely self-evident, so this is adequate but adds little beyond the schema.

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 a specific verb (read) and resource (one generation with its results) and enumerates the returned content (prompt, model, settings, inputs), with the API mapping GET /generation/{id}. It is clear on its own but does not differentiate from close siblings such as mcp_read_generation_result, get_generation_results, or get_generation_status.

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?

The phrase "for the result viewer's Info panel" implies a usage context, but there is no explicit when/when-not guidance and no alternative tool is named. An agent must infer when to pick this over the other generation-reading siblings.

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