separate_audio

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

Annotations already cover readOnly=false, destructive=false, idempotent=false, and openWorld=false. The description adds useful behavior beyond the annotations: it awaits verified outputs and warns that long work should use start_separation; it does not detail timeout behavior or filesystem side effects, though output schema and schema descriptions carry some of that context.

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, front-loaded with the primary action and immediately followed by the alternative. There is no wasted text.

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 tool is complex with many nested options and writes outputs, but the description supplies the key selection and synchronous-await context. Input schema and output schema carry the detailed parameter and return semantics; the main minor gap is that 'verified outputs' is not further explained.

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 100%, so every parameter is documented in the input schema. The description adds no parameter-specific syntax, defaults, or selection advice beyond the start_separation routing hint, so the baseline of 3 applies.

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 pairs a specific verb ('Run') with a bounded resource ('one separation') and distinguishes single synchronous work from start_separation. It does not explicitly say 'audio' or call out every specialized separation sibling, but the scope is clear enough to select the tool.

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 second sentence explicitly routes long work to start_separation, which implies this tool is for shorter or blocking runs. It lacks explicit exclusions against separate_ensemble, separate_chain, or separate_batch, but the 'one separation' framing distinguishes those cases.

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