mcp_opendaw_apply_sidechain

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

With no annotations, the description provides good transparency: it creates volume automation events on the target track's volume parameter, and details return info (total events, ducking pattern). It lacks mention of whether existing automation is overwritten.

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 purpose line, context, parameter list, return info, and example. It is slightly lengthy but each 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?

Given the tool's complexity (8 params, 1 required, output schema present), the description covers most aspects: how it works, parameter roles, return values, and example. Minor gap: no mention of prerequisites (e.g., need an existing kick track).

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?

All 8 parameters are explained with definitions, example values, and ranges, compensating for the 0% schema description coverage. For instance, depth: '0.6 = volume drops to 40% on each kick, 0.8 = drops to 20%'.

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 states the tool applies sidechain ducking via volume automation, specifying the classic pumping/breathing effect. It distinguishes from sibling tools like mcp_opendaw_connect_sidechain by focusing on simulation via automation.

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 when to use the tool (for house, techno, EDM, pop) and how it works, but does not explicitly state when not to use it or alternative tools like actual sidechain compression via connect_sidechain.

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