mcp_opendaw_repeat_notes

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

No annotations exist, so the description carries full burden. It discloses that notes are copied, transforms (time, pitch, velocity) are applied cumulatively per repeat, and structure is preserved. However, it does not explicitly state whether the source region is modified or if the operation is reversible, which would increase 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 with a concise summary paragraph followed by a clear Args list. Every sentence adds distinct value without redundancy. No fluff exists.

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 9 parameters, no annotations, and an output schema (so return values not needed), the description covers all parameters with examples, defaults, and cumulative behaviors. It also compares to a sibling tool, making the context complete for agent decision-making.

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 coverage is 0%, but the description compensates fully. Every parameter is explained with default values, valid ranges (e.g., repeats 1-16), cumulative effects (transpose_semitones, velocity_decay), and behavioral details (direction affects sign). The Arg block adds meaning beyond the bare 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 repeats notes N times with per-repeat transformations, includes the specific verb 'repeat', identifies the resource as 'notes in a region', and distinguishes from create_midi_echo by highlighting differences in decay versus uniform transform. Use cases like sequences and ostinato patterns further clarify 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?

The description explicitly contrasts this tool with create_midi_echo, indicating when to use it (preserving note structure, uniform transforms) versus alternatives (decaying feedback). It implies usage for sequences and motivic development but does not provide explicit when-not-to-use scenarios or prerequisites beyond the required parameters.

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