synthesize_batch

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

With no annotations provided, the description carries the full disclosure burden and does it well. It reveals defaults (rate=90, merge=false, auto_play=true, pause_ms=500), provider-specific voice defaults, the auto-select behavior when language is given without voice, the side effect of opening files via auto_play, and the exact return format. It does not mention overwrite behavior or rate limits, but for a synthesis tool this is a strong disclosure.

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 organized as a docstring with an opening one-sentence summary, a clean Args list, and a Returns section. Despite covering many parameters, every line adds value and the structure makes it easy to scan. No filler or tautology is present.

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 complexity of 12 parameters and no annotations, the description covers essentially everything needed to call the tool: all params, defaults, merge behavior, return payload, and output location. It stops short of stating file overwrite policy or constraints on input array size, but these are minor for the tool's context.

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 0%, so the description must compensate for all 12 parameters. It does so thoroughly: each parameter gets a clear meaning, default, or conditional behavior beyond the raw schema. For example, it explains the [tired]/[whisper] audio tags for texts, provider-specific voice defaults, and the role of pause_ms when merging. This fully bridges the schema gap.

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 states a specific verb and resource: 'Synthesize multiple texts to MP3 files.' This clearly establishes the batch nature of the tool and the output format. However, it does not explicitly distinguish itself from sibling tools like synthesize_pair_batch, so an agent must infer the differentiation from the word 'multiple' and merge semantics.

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 implies batch usage by saying 'multiple texts' and describing merge behavior across texts, but it never explicitly states when to choose this tool over siblings such as synthesize or synthesize_pair. It offers no exclusions or alternative routing, so the usage context is present only implicitly.

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