mcp_opendaw_groove_transfer

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

The description details the algorithm (extracts average timing offsets and velocity ratios, applies them to destination notes) and notes that it modifies timing and velocity. However, with no annotations, it doesn't disclose potential side effects (e.g., irreversibility, prerequisite conditions) beyond the core mutation.

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 with a clear first sentence, a concise algorithm explanation, and a structured parameter list. While a bit long, every sentence adds value, and the parameter list is necessary given the 0% schema coverage.

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 all parameters, the algorithm, the distinction from copying, and mentions return values ('Returns groove template stats and per-region modification counts'). It lacks explicit prerequisites (e.g., source and destination regions must exist with notes), but overall it's sufficient for an agent to select and 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 provides a complete per-parameter explanation with defaults and ranges (e.g., 'timing_strength: 0-1, how much timing offset to apply'), fully compensating for the schema's lack of semantics.

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 explicitly states 'Transfer groove (timing + velocity feel) from a source region to a destination region' and clarifies 'This is NOT copying notes — it transfers the *feel*,' distinguishing it from note-copying tools and providing a specific, actionable purpose.

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 gives context with 'A 1-bar drum groove can be applied to a 4-bar programmed pattern' and explains how the groove cycles, but does not explicitly mention alternatives like quantize or humanize, nor when not to use it. Clear context but no exclusions.

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