setup_parallel_compression

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

With no annotations, the description carries the full burden. It explains the outcome (bus creation, routing) and parameter impact (fast attack for tight pumping) but does not detail side effects, permissions, or potential destructive behavior beyond creating a bus.

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 summary line, use context, and a parameter list. It is appropriately detailed for 8 parameters, but could be slightly more concise (e.g., merging some parameter notes).

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?

Given no annotations and no output schema, the description covers purpose, typical values, and usage. It omits prerequisites (e.g., existing tracks) and error handling, but is reasonably complete for a setup tool.

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?

The description thoroughly explains each parameter with typical values and purpose (e.g., 'send_db: Send level from each source to the bus (0 = unity)'. Since schema coverage is 0%, this fully compensates and adds significant meaning beyond type/default.

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 starts with a specific verb+resource: 'Create a NY-style parallel compression bus and route source tracks to it.' This clearly distinguishes it from sibling tools like setup_drum_bus or setup_vocal_chain, which serve different purposes.

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 provides a classic use case (crushing drums/vocals and blending) and explains the benefit (density/power without destroying transients). It implicitly tells when to use but lacks explicit when-not-to-use or alternative tools.

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