voicebox_export_generation

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

No annotations exist, but the description only says 'Export... as JSON'. It does not disclose whether the JSON is returned directly, saved to a file, or any side effects. Behavioral traits like permissions or data scope are absent.

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?

Single sentence, clear and front-loaded with the action. No unnecessary words.

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?

Output schema exists, so return format need not be detailed, but the description lacks context about the generation lifecycle, when export is valid (e.g., after generation completes), and error conditions. Adequate for a simple tool but minimal.

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% (one parameter documented). The description adds 'metadata + settings' context but does not enhance parameter documentation beyond the schema. Baseline 3 is appropriate.

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 clearly states the tool exports a generation's data as JSON, specifying 'metadata + settings'. This distinguishes it from siblings like voicebox_export_generation_audio, which exports audio.

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 guidance on when to use this tool versus alternatives (e.g., vs voicebox_export_generation_audio or get_generation). No mention of prerequisites or exclusions.

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