add_parallel_compression

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

With no annotations provided, the description carries the behavioral burden. It usefully states that a bus is created and that the original track remains untouched, which is valuable signal-flow context. However, it omits whether the operation is reversible, whether it modifies project state beyond creating a bus, and what permissions or side effects are involved.

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 a single efficient sentence with no filler. It is not explicitly front-loaded with an action verb, but the concept is immediately clear and appropriately sized for the tool.

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 explains the audio concept but does not provide usage context, alternatives, or operational details such as mutation scope. Since the schema fully documents the three parameters and no output schema exists, the main remaining gap is guidance on when and why to invoke this tool versus its many siblings.

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 the schema already documents track, blend_db, and compressor thoroughly. The description adds no parameter-level meaning, but baseline 3 is appropriate when the schema carries parameter semantics.

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 identifies the effect being added: a New York-style parallel compression bus with a heavily compressed copy blended under the original. The name supplies the verb, and the description supplies the specific audio-processing concept. It does not, however, distinguish this tool from sibling routing or FX tools such as add_fx or setup_sidechain.

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 explains what parallel compression is but gives no explicit guidance on when to use this tool versus alternatives like add_fx, setup_sidechain, or create_bus. It also does not mention prerequisites such as track selection or mix context. Usage must be inferred entirely from the tool name and concept.

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