mcp_opendaw_repeat_notes

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

With no annotations, the description carries the full burden of disclosing behavior. It explains the copy-and-transform mechanic, cumulative parameter effects (transpose, velocity decay, time gap), and note-structure preservation. However, it does not explicitly state whether original notes are retained or replaced, which is a minor transparency gap.

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: a one-sentence summary, a behavioral explanation, and a detailed parameter list. Every sentence adds operational value, and the Args section is essential given the sparse schema. There is no filler or repetition.

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?

For a tool with 9 parameters, no annotations, and an output schema, the description covers purpose, mechanics, parameter semantics, and usage context. It omits edge cases (e.g., behavior when region has no notes) but overall provides sufficient detail for an agent to invoke it 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?

The schema has 0% description coverage, but the Args section fully compensates by documenting all 9 parameters with units, ranges, and behavioral meaning (e.g., velocity_decay: '0=fade out, 1=constant, 0.8=gradual fade'). This is far richer than the bare schema definitions.

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 'Repeat existing notes in a region N times with per-repeat transformations', specifying the verb, resource, and scope. It explicitly contrasts with create_midi_echo, distinguishing this tool from a sibling and eliminating ambiguity about its function.

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 names create_midi_echo as an alternative and explains the difference: 'Unlike create_midi_echo (which decays feedback repeats), this tool preserves note structure and applies a uniform transform per repeat cycle'. It also lists ideal use cases (sequences, ostinato patterns, motivic development), giving concrete guidance on when to choose this tool.

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