setup_sidechain_compression

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

No annotations are provided, so the description carries the full burden. It usefully discloses the two mutations performed (creating a send and configuring ReaComp) plus the volume default, but says nothing about idempotency, reversibility, failure modes if no ReaComp exists at the given index, or what the returned 'complete setup info' actually contains.

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?

Front-loaded with the one-line capability statement, then Args/Returns/Example. The Returns line ('Object with complete setup info') is vague filler, but the rest earns its space by documenting otherwise-undescribed parameters.

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?

For a 4-parameter mutation tool with no annotations and no output schema, the description covers purpose, parameter meaning, and a worked example well. It is only thin on failure/edge behavior and return shape, which are the remaining gaps.

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% and the schema carries no descriptions, so the description must compensate — and it does, explaining the role of each of the four parameters (trigger vs. target track, ReaComp FX index, send volume in dB with default) and grounding them in the example.

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?

States a specific verb+resource ('creates send and configures compressor') and explicitly positions itself as the 'all-in-one function' for sidechain compression, which cleanly distinguishes it from the granular siblings create_send, set_send_volume, setup_sidechain_send, and configure_reacomp_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 'all-in-one' framing and the concrete kick-triggered-bass example convey when this composite tool is the right pick over the atomic siblings. It does not, however, explicitly say when *not* to use it or name the alternatives it replaces.

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