mcp_opendaw_apply_sidechain

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 clearly states that it creates automation events on the volume parameter and returns the event count and pattern info. However, it does not disclose potential side effects such as whether existing automation is overwritten or appended, whether the operation is reversible, or any preconditions like unit/track existence.

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?

Well-structured and front-loaded with a one-line summary. The mechanism, parameter list, return info, and an example are all included, and each sentence serves a purpose. The parameter explanations double as usage guidance, keeping the description efficient.

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?

Covers purpose, mechanism, parameters, return value, and an example. With the output schema present, describing return details in more depth is unnecessary. Missing only brief preconditions (e.g., valid unit_index/track_index, potential need for existing AU), but overall complete for an 8-parameter 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?

Schema coverage is 0%, and the description fully compensates. Every parameter (unit_index, track_index, bars, start_beat, depth, attack, release, kick_interval) is explained with meaning, ranges, and practical examples—e.g., depth: '0.6 = volume drops to 40% on each kick'—adding far more value than the bare schema.

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?

Uses a specific verb+resource: 'Apply sidechain ducking via volume automation'. Clearly distinguishes from the sibling connect_sidechain tool by stating it 'Simulates sidechain compression' rather than performing actual routing, and from set_track_volume by describing automation creation.

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?

Provides clear context by describing the effect as 'the signature sound of house, techno, EDM, and modern pop', implying when this tool is appropriate. The description of how it works ('by creating volume automation') implicitly differentiates it from real sidechain tools, but it does not explicitly state alternatives or when not to use it.

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