Get audio render

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

Annotations already declare readOnlyHint and idempotentHint, so the description does not need to repeat that. It adds the constraint that only 'recent' renders are accessible, plus the output format (WAV), which is useful. However, it does not disclose potential errors or further behavioral details, so it adds only modest value beyond annotations.

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 that communicates the action, resource, and identifier without waste. It is highly concise and well-structured.

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 retrieval tool with one parameter and no output schema, the description is nearly complete. It names the output (WAV file) and the input (render ID), and the annotations cover safety semantics. It does not describe error cases, but given the simplicity, this is a minor gap.

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% (the schema has no description for renderId). The description mentions 'by render ID' but does not compensate for the lack of parameter details—it merely references the parameter name without explaining its meaning, format, or any constraints beyond the schema's minLength and type.

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 a specific verb 'Retrieve' and names the resource 'rendered WAV file' with a clear identifier ('by render ID'). This distinguishes it from sibling tools like update_audio_clip or render_audio, which are mutation or creation actions.

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 usage when one has a render ID and needs the WAV file, but it does not explicitly state when to use this tool instead of alternatives or provide any exclusions. The word 'recent' hints at a limitation, but it is not elaborated.

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