mcp_opendaw_create_tempo_ramp

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

No annotations are provided, so the description carries full burden. It explains the mechanism (linear interpolation, multiple ValueEventBox events), return value (events created, config, BPM preview), and defaults (steps=16). It lacks details on side effects or permissions but is sufficiently transparent for a creation 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 well-structured: purpose, mechanism, parameter list, return info, examples. Each sentence adds value without redundancy. It's comprehensive yet concise.

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 (6 parameters, 4 required, output schema exists), the description covers purpose, all parameters with details, return value, and examples. It provides enough information for an AI agent to use 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 explains all 6 parameters: start_beat, end_beat, start_bpm, end_bpm, curve (with options and default), steps (with effect of fewer steps). Three examples demonstrate usage. This fully compensates for the lack of parameter descriptions in 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 'Create a smooth tempo ramp (ritardando or accelerando) across a beat range.' It specifies the verb (create), resource (tempo ramp), and musical context. It distinguishes from sibling tool add_tempo_change by noting it creates multiple events for a smooth curve.

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?

It provides context for use: 'essential for expressive transitions, endings, and dramatic section changes.' It compares to add_tempo_change (single event vs multiple). While it doesn't explicitly state when not to use, the guidance is clear enough.

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