mcp_opendaw_create_canon

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

With no annotations, the description carries full responsibility. It explains the core behavior (same melody copied into voices, time-delayed entries, optional transposition, velocity decay) and lists return values (notes created, voice count, total length, transpositions). It does not state whether the operation is additive or destructive to existing notes, or mention prerequisites for the target track, which would have made it fully transparent.

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 long but well-structured: a definition, musical context, and one-line parameter definitions. Every sentence adds value, especially given the lack of schema descriptions. It is slightly verbose in the conceptual opening but not wasteful.

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 complexity of 10 parameters, no annotations, and 0% schema description coverage, the description is remarkably complete. It covers all parameters, returns, examples, and a sibling differentiation. The presence of an output schema means return values need not be fully enumerated, but the description still summarizes them.

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%, so the description must compensate. It does so thoroughly: all 10 parameters are explained with concrete examples, ranges, and defaults (e.g., transposition '0,7,12', voices 2-6, entry_delay_beats 1-16). This is exemplary compensation for missing schema descriptions.

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 opens with a clear, specific verb and resource: 'Create a canon — strict melodic imitation with delayed voice entries.' It explicitly contrasts with the sibling create_counterpoint ('which generates a new line'), clearly distinguishing what this tool does and making the purpose unmistakable.

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 provides strong usage context with musical examples (Pachelbel, Row Row Row Your Boat) and an explicit alternative comparison to create_counterpoint. However, it doesn't enumerate exclusions for other close siblings like create_fugue or create_chorale, so the guidance is clear but not exhaustive.

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