mcp_opendaw_create_volume_fade

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 discloses that the tool creates automation events on the AU volume parameter, ramps between dB levels, uses an exponential curve by default, and returns events created, fade config, and dB range. It does not mention side effects like overwriting existing automation, but the core behavioral traits are well-covered.

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 concise and well-structured: a clear opening sentence, a brief usage context, a parameter list with defaults, a note on return value, and two concrete examples. Every sentence adds value, and the key information is front-loaded.

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 8 parameters, no annotations, and the presence of an output schema (indicated but not shown), the description is remarkably complete. It explains the tool's purpose, all parameters with defaults, the curve types, the return structure, and provides examples. No obvious gaps for an agent to invoke the tool correctly.

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%, but the description compensates fully by listing all 8 parameters with explanations, defaults, and examples (e.g., unit_index, direction, start_beat, duration_beats, start_volume_db, end_volume_db, curve, steps). This provides complete semantic meaning beyond the 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?

The description clearly states the tool's purpose: 'Create a volume fade automation on an audio unit — fade in or fade out.' It uses a specific verb ('create') and resource ('volume fade automation'), and the context ('common mix technique') helps distinguish it from other automation tools. The tool name itself is also specific.

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 includes usage context: 'The most common mix technique for intros, outros, breakdowns, and section transitions.' This guides when to use it, but it does not explicitly state when not to use it or compare it with alternatives like add_automation or create_automation_event. Given the clear context, it is still helpful.

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