Render audio

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description adds context: 'offline-render' signals it is not real-time, and 'stereo 16-bit WAV' gives output format. This is useful 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 sentence that front-loads the action, format, and return value. No filler or redundancy.

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 tool with 3 optional parameters and no output schema, the description explains the return behavior ('return playable audio') and high-level operation, but the missing parameter semantics create a gap. It is largely complete for calling with defaults but insufficient for parameter customization.

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 schema describes 3 parameters, but the description does not explain any. With 0% schema description coverage, the description should compensate but does not. For example, 'bars' behavior (total vs loop length) is ambiguous; 'name' and 'sampleRate' are intuitive but not clarified.

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 'render' with a clear resource ('the current project') and specifies output as 'a stereo 16-bit WAV file and return playable audio.' This distinguishes it from 'export_project' which likely saves to disk, though no sibling is explicitly named.

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?

No explicit when-to-use guidance or exclusion of alternatives. The phrase 'return playable audio' implies it is for immediate playback vs exporting, but it is not explicit. Sibling tools like export_project and get_render could benefit from differentiation, but that is absent.

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