generate_audio

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

Describes return format (base64 MP3, per-mark UUIDs, millisecond timings) and invocation of cwtts. Lacks details on potential side effects or rate limits, but sufficient for a generation 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?

Efficient two-paragraph structure with zero wasted words, front-loaded with key purpose and return info followed by parameter details.

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?

Covers purpose, usage context, output format, and parameter semantics completely. With output schema present, return value details are adequate without needing exhaustive documentation.

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 crucial meaning to both parameters: language codes listed explicitly, marks described as 'Pre-split sentence list', far beyond the bare schema types.

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 generates audio by calling cwtts directly, distinguishes from sibling `create_chapter_from_marks` by positioning this as a break-glass alternative.

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 says 'Break-glass' for emergency use and directs normal chapter creation to the sibling tool, providing clear when-to-use and 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.