mcp_opendaw_create_volume_fade

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

With no annotations, the description carries the full behavioral burden. It discloses that the tool creates volume automation events, ramps between dB levels, uses an exponential curve by default, and returns specific data. It does not mention whether it overwrites existing automation or is reversible, but it gives a clear operational picture for a mutating tool.

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 organized in a logical flow: opening purpose, usage context, parameter list, return value, and examples. Every sentence serves a purpose; the parameter documentation and examples justify the length. It front-loads the core information and avoids fluff.

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 complexity (8 parameters, no annotations, no schema descriptions), the description covers all essential aspects: what it does, when to use it, all parameters with defaults, and return values. The presence of examples further enhances completeness, leaving little ambiguity for an AI agent.

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 0%, so the description fully compensates. It explains every parameter with units, defaults, and directional dependencies (e.g., start_volume_db default 0 for fade out, -60 for fade in), and provides two concrete examples that clarify usage. This exceeds the schema's bare titles.

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 verb ('Create a volume fade automation') and the resource ('audio unit'), explicitly covering both fade directions. It distinguishes itself from sibling tools like create_filter_sweep, create_pan_sweep, and set_audio_region_fade by focusing on volume automation on the AU's volume parameter.

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 clear context for when to use this tool: 'The most common mix technique for intros, outros, breakdowns, and section transitions.' It does not explicitly mention alternatives or when not to use it, but the stated context is sufficient to guide selection.

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