Generate audio

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

No annotations are provided, so the description carries the full burden. It discloses cost scaling with duration and mentions async via the `wait` parameter. However, it does not detail mutability, idempotency, failure behavior, or output format, leaving gaps for a tool with no annotations.

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?

Two sentences efficiently convey purpose, model support, a key parameter hint, and cost note. No wasted words, front-loaded, and easy to parse. Every sentence earns its place.

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?

With 7 parameters, no output schema, and no annotations, the description covers the main purpose, key constraints (duration snapping, lyrics for MiniMax Music), cost, and async behavior. It adequately prepares an agent to use the tool, though output format is implied but not explicit.

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%, so baseline is 3. The description adds meaningful context: 'For MiniMax Music pass `lyrics`' and 'ElevenLabs Music requires this and only accepts 30 or 60 — auto-snapped to the nearer value.' It also explains the `wait` parameter behavior. This extra info improves parameter understanding.

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 'Generate speech or music' with specific models (ElevenLabs V2/V3/Music, MiniMax Speech/Music). This distinguishes it from sibling tools like generate_image or generate_video, providing a specific verb+resource pairing. It also notes cost scaling with duration, adding clarity.

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 gives a specific usage hint: 'For MiniMax Music pass `lyrics`' and mentions cost behavior. However, it lacks explicit guidance on when to use this tool versus siblings or scenarios to avoid. The context is clear but without alternatives or exclusions.

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