get_generation_status

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

With no annotations, the description is the only behavioral signal, and it indicates a read-only operation via 'Return.' However, it does not mention error behavior, idempotency, or what happens when the generation_id is invalid, leaving the agent with limited understanding of the tool's side effects and failure modes.

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 redundant information. Every word contributes to clarifying the tool's purpose, making it highly efficient for agent reading.

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?

This is a simple status-retrieval tool with one required parameter and an output schema, so the description does not need to explain return values. It covers the essential purpose, though it omits hints about polling behavior or invalid IDs; still, the overall context is adequate for a getter 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?

The description refers to 'a generation,' which naturally maps to the generation_id parameter, but it does not explain how to obtain or format the ID. Given 0% schema description coverage, the description adds minimal value beyond the parameter name's self-evident meaning.

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 'Return' and names the resource as 'state and asset metadata for a generation,' clearly defining the tool's action. This distinguishes it from sibling tools that generate music or sound effects, which are about creation rather than status retrieval.

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 description implies the tool is used to check on an existing generation, likely after using one of the generation siblings. It does not explicitly state when not to use it or name alternatives, but the context is clear enough for an agent to infer the appropriate scenario.

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