mcp_opendaw_clone_track

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 that a new track is created, optionally in a new audio unit, and details parameter effects (transpose, velocity scale, time offset). It does not mention potential limits or undo behavior, but it is largely transparent about the core actions.

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 summary, clarification, comparison, use cases, and parameter list. The use case list is slightly long but adds value. The content is informative without being overly verbose, though could be slightly more 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?

An output schema exists, so return values are not needed. The description covers tool behavior, when to use, and parameters. It does not explicitly mention error conditions or prerequisites (e.g., track must exist), but the required parameters imply these. Overall, it is fairly complete for a cloning tool.

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 (no parameter descriptions). The tool description compensates with an 'Args' section that explains each parameter, including ranges, defaults, and semantics (e.g., transpose -24 to +24, velocity_scale 0.1-2.0). This adds significant meaning beyond 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 'Clone a track — full duplication of notes, regions, and structure.' It further explains that it creates a new track from scratch with all notes, and explicitly distinguishes from copy_notes_to_track. The use cases (doubling, octave layering, etc.) reinforce the 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 directly contrasts clone_track with copy_notes_to_track, stating when to use each. It also lists essential scenarios (doubling, octave layering, parallel harmony, etc.) providing clear guidance on when this tool is appropriate.

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