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

Annotations already declare the safe read profile (readOnly, idempotent, non-destructive), and the description adds real behavioral context beyond them: the status lifecycle values, that result fields only populate once succeeded, and the Music-specific 'one take per call, take_group ties the two' partial-result semantics. It stops short of stating polling expectations or what a failed/canceled response contains.

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?

Two sentences, front-loaded with the core action and required id provenance before the return-value detail. The parenthetical status enum list adds length, but it earns its place by telling the agent which states to expect when polling. Minor density cost only.

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?

An output schema exists, so return values needn't be spelled out, yet the description usefully flags the conditional fields and the take_group relationship for Music. Combined with annotations covering the safety profile, an agent has enough to call it correctly; only explicit guidance on when to prefer list_generations is missing.

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 coverage is 100% for the single id parameter, so the schema already documents its origin ('from generate or list_generations'). The description repeats that provenance without adding format, validation, or failure behavior for an unknown id. Baseline 3 applies when the schema carries the parameter burden.

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?

Names a specific verb (Read) and resource (one generation) and immediately scopes it against the sibling list_generations by saying 'one generation'. It also enumerates the payload surface (status, progress, result URL, preview, size, length), so an agent knows exactly what it retrieves.

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 implied rather than stated: 'Read one generation' plus the id's provenance ('from generate or list_generations') tells the agent this is the single-item counterpart to the list tool. There is no explicit when-to-use / when-not-to-use guidance and no routing to get_run, get_cut, or cancel_generation for related follow-ups.

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