voicebox_save_capture_audio

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

With no annotations, the description carries full burden for behavioral disclosure. It only states the basic action of downloading and saving to a file. It lacks details on whether the file will be overwritten, if any permissions are needed, or what happens on failure. Without annotations, this is insufficient.

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?

A single sentence that is concise and front-loaded. However, it could benefit from expanding to cover key behavioral details without being verbose. It earns points for efficiency.

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?

Given the presence of an output schema (not shown) and the simple nature of the tool, the description is minimally adequate. It covers the core operations but misses important context like whether the file is created/overwritten, expected formats, or confirmation of success. A score of 3 reflects mediocrity.

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 100%, so baseline is 3. The description adds minimal extra meaning beyond the schema—it confirms that the action involves downloading and saving, but doesn't explain why capture_id and output_path are used or their formats. A score of 3 is appropriate as it meets the baseline but adds little value.

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 action ('download and save') and the resource ('capture's audio'). It distinguishes from some siblings (e.g., voicebox_save_version_audio) by specifying capture, but it doesn't explicitly differentiate from similar tools like voicebox_save_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 is provided on when to use this tool versus alternatives like voicebox_save_version_audio or voicebox_save_sample_audio. It doesn't state prerequisites, limitations, or when not to use this tool.

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