audio_synthesize

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

No annotations are provided, so the description carries full burden. It describes the process and supported effects but does not mention file overwrite behavior, performance considerations, or permissions. It is transparent about what it does but lacks potential behavioral details.

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 well-structured with a brief summary followed by a parameter list. Every sentence adds value, no unnecessary words. Efficient and clear.

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?

The description covers all parameters, effects, and return value. Minor omission: no mention of file overwrite behavior or limitations (e.g., max duration). However, given complexity, it is largely complete.

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 add meaning. It provides defaults and detailed explanation of the effects parameter with sub-keys (envelope, fade_in, fade_out, reverb, lowpass). This significantly enhances understanding beyond the bare schema.

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 audio procedurally using synthesis' and 'Creates WAV files from scratch using mathematical waveforms'. It distinguishes from siblings like audio_compose (which likely composes existing audio) by emphasizing no external audio files needed.

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 usage for generating audio from scratch using synthesis, but does not explicitly state when to use this tool vs alternatives like audio_compose or audio_effects. No 'when not to use' or direct comparisons.

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