mcp_opendaw_groove_transfer

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 extraction and application process: 'Extracts the groove template... then applies this template to destination notes — shifting their timing and scaling velocity.' However, it does not specify whether the operation is destructive or reversible, nor does it mention the effect on the source region. The mention of return values (groove template stats) adds some transparency.

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, starting with a high-level summary, then detailing the process, and finally listing parameter explanations. While it is somewhat lengthy, every sentence adds value. A slightly more compact format (e.g., table for parameters) could improve conciseness, but it remains clear and 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 the 10 parameters and the presence of an output schema, the description covers all parameters thoroughly and explains the non-obvious concept of groove cycle. It mentions return values. However, it lacks discussion of prerequisites (e.g., must have notes in source region) and edge cases (e.g., groove_length exceeding region length), leaving some gaps.

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?

The input schema has 0% description coverage, so the description fully compensates by providing detailed explanations for all 10 parameters. It includes concrete examples (groove_length: '4 = 1 bar of 4/4, 3 = waltz, 2 = half-bar'), ranges (timing_strength: 0-1), and allowed values (grid: '16th' or '8th'). This adds significant meaning beyond the schema's titles and defaults.

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: 'Transfer groove (timing + velocity feel) from a source region to a destination region.' It distinguishes this from copying notes by explicitly stating 'This is NOT copying notes — it transfers the *feel*.' The example of applying a 1-bar drum groove to a 4-bar pattern further clarifies the scope.

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 this tool by explaining the concept of groove transfer and contrasting it with note copying. It gives an example scenario (1-bar groove to 4-bar pattern). However, it does not explicitly list alternatives or state when not to use it relative to sibling tools like apply_swing or humanize_notes.

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