audio_compose

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

With no annotations, description provides basic behavior (mixing, volume, loop, output) but lacks error handling, file constraints, or mixing details like sample rate handling. Incomplete for full transparency.

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?

Efficiently structured with a one-line summary followed by structured args and returns. No unnecessary words; every sentence adds value.

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 all parameters and return value. Lacks details on looping behavior (what happens when loop=true?) and error cases. Good but could be more complete for a 3-param tool with no annotations.

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 fully compensates by explaining each parameter: tracks as list of configs with file, volume, start, loop; duration as total seconds; output_path as absolute path. Adds crucial meaning.

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 it layers multiple audio tracks with volume mixing, distinguishing it from siblings like audio_effects or audio_synthesize. The verb 'layer' and resource 'audio tracks' are specific.

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?

Implied usage for mixing multiple WAV files with volume control, but no explicit when-to-use or when-not-to-use guidance. No alternatives mentioned despite many sibling audio tools.

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