mcp_opendaw_create_pan_sweep

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

No annotations are present, so the description carries the full burden. It discloses the core behavior (creates automation events on the AU's panning parameter) and explains default curve choice, plus it states the return value. However, it does not mention whether existing automation is overwritten, if the operation is undoable, or any required permissions, leaving some important side effects undocumented.

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-organized: a one-sentence summary, a use-case paragraph, a clear parameter list, return type mention, and two concrete examples. Every sentence adds valuable information, and the front-loaded summary ensures the agent quickly understands the tool's purpose.

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?

The description covers the essential details needed to invoke the tool correctly: parameters, defaults, return value, and examples. It does not address edge cases like invalid unit_index or behavior when existing automation overlaps, but these are minor for a focused pan-sweep tool. The presence of an output schema also reduces the need to explain return details.

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?

With 0% schema description coverage, the description fully compensates by defining every parameter: unit_index, start_beat, duration_beats, start_pan/end_pan ranges (-1.0 to 1.0), curve options, and steps. It also provides practical examples that demonstrate how to call the function, exceeding what the schema titles alone offer.

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 begins with a clear, specific verb ('Create a panning automation sweep') and resource ('panning parameter'), explicitly stating the action's scope. It distinguishes itself from sibling tools like create_filter_sweep and create_volume_fade by focusing on panning movement, making the tool's purpose unambiguous.

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 on when to use the tool, citing it as a classic technique for intros, guitar solos, EDM builds, and section transitions. It does not explicitly state exclusions or alternatives (e.g., when to use set_track_panning instead), but the context is strong enough to guide an agent toward appropriate usage.

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