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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: the polling cadence, the terminal state, and the warning against re-running generation while rendering. It stops short of describing failure/timeout behavior, which keeps it from a 5.

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?

Front-loaded with the core purpose, then the polling loop, then the secondary path. Two long sentences plus an imperative warning, all of which carry information. Slightly dense but no filler.

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?

With no output schema, the description steps in by naming the return fields (playable audio_url, duration_seconds, generation_id) and the status transitions. Combined with full schema coverage and annotations, an agent has enough to call it correctly; only error/timeout handling is unaddressed.

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%, so the baseline would be 3, but the description genuinely enriches the parameters by explaining where each id originates ('request_id from a rendering generate_audio answer', generation_id from a finished take via generate_audio or list_my_audio) and that they are alternatives. That is more than the schema restates.

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 and resource ('Collect one of your finished audio takes') and immediately frames it as a polling/fetch tool, which clearly separates it from generate_audio and list_my_audio. It does not explicitly name siblings, but the workflow position is unambiguous.

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?

Gives an explicit trigger (generate_audio returned status 'rendering' with a request_id), an explicit cadence (every 15 seconds until status 'done'), an explicit alternative path (fetch an earlier take by generation_id), and an explicit prohibition ('Never re-run the line while it is rendering'). Nothing is left to inference.

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