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

The annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful context by listing the returned fields, including charged credits and failure refund status, but it does not describe authentication requirements, behavior for unknown generation IDs, or whether repeated polling has any side effects.

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 description is a single front-loaded sentence with no filler or redundant restatement of the tool name. Every listed item adds information about what the tool returns.

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?

The tool is simple, with one required parameter and no output schema, so the description's enumeration of return fields is helpful. Still, it omits the meaning of generation_id and does not indicate failure behavior when the ID is invalid or not found, leaving gaps for a retrieval 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%, so the description carries the burden of explaining the required generation_id parameter. It does not explicitly state that generation_id identifies the generation whose progress and result are being read, leaving the parameter's meaning to inference from the tool name.

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 uses the specific verb 'Read' and names the exact data returned: progress, result URLs, charged credits, and failure refund status. This makes the tool's purpose clear, though it does not explicitly say it retrieves a single generation by ID or contrast itself with siblings like list_generations.

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 mention of 'progress' and 'result URLs' implies the tool is used to check the status or outcome of an existing generation. However, there is no explicit guidance on when to use it versus list_generations or get_generation_capacity, and no stated exclusions or polling recommendations.

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