Generate voiceover

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

Discloses cost (credits by length) and character limit (≤900). Annotations are all false, which is consistent with description. Could mention if idempotent or not, but that's minor.

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?

Reasonably concise with front-loaded purpose. Three sentences fitting the necessary information without excess.

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 tool complexity and full schema coverage, description covers purpose, parameters, usage guidelines, cost, limitations, and sibling differentiation. Output schema exists but not needed to explain return value.

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?

Adds meaning beyond schema: explains engine options, voice presets from capabilities, default engine, character limit. Schema coverage is 100%, so description adds 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 tool's purpose: raw text-to-speech from voice-model catalog, returning MP3 URL. It distinguishes from sibling tools like render_ad and generate_video.

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?

Explicitly states when to use (standalone voiceover/narration) and when not (not for adding audio to video), and names alternative tools (render_ad, generate_video, change_voice).

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