vocea_get_audio

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

No annotations are provided, so the description carries full burden. It merely states the action without disclosing behavioral traits such as read-only nature, error conditions for invalid audio_id, or side effects. Lacks depth.

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?

One sentence of 9 words, front-loaded with the verb 'Get'. Every word earns its place with no 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?

Given no output schema and a simple tool, the description is minimally adequate but fails to detail what 'details' include beyond CDN URL. It does not specify response structure, leaving gaps for the agent.

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 single parameter audio_id has no schema description, and schema coverage is 0%. The description adds minimal context by referring to 'a previously generated audio', which implies audio_id identifies that audio, but does not specify format or origin.

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?

Clearly states the tool retrieves details including CDN URL for a previously generated audio, with a specific verb and resource. It distinguishes itself from sibling tools like vocea_generate_audio (creation) and vocea_list_voices (listing).

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?

Implies usage after audio generation by stating 'previously generated audio', but provides no explicit guidance on when to use this tool versus alternatives like vocea_get_credits or quando not to use it.

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