generate_audio

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

With no annotations, the description carries the full burden. It mentions 'unlimited' and the model, but fails to disclose other behavioral traits like rate limits, error behavior, or output format. The statement about a 'verified contract' is vague and incomplete.

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 concise at three lines, but the second line is cryptic and could be streamlined. No waste, but clarity could be improved.

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 10 parameters, 0% schema coverage, no annotations, and an output schema not described, the description is inadequate. It fails to provide a complete picture for effective tool use.

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 0%, so description must compensate. It mentions prompt (not text), model, voice_id, voice_type, but contradicts the schema (model vs tts_model). It does not explain most parameters (wait, timeout, download, account, extra_params), leading to potential confusion.

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 generates audio from text using a specific model (text2speech_v2), distinguishing it from sibling tools like generate_image or generate_video. The verb 'generate' and resource 'audio' are explicit.

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?

The description provides some usage context (unlimited, works with Turkish and other languages, get voice_id from list_voices) but does not explicitly state when to use this tool versus alternatives or give when-not-to-use guidance.

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