mcp_opendaw_create_canon

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

With no annotations provided, the description carries full responsibility. It describes the core behavior: copying a melody into multiple voices with time and pitch shifts, and notes return values. However, it does not explicitly state whether the tool is destructive or read-only, or if it modifies existing track content versus creating new regions. Still, it is fairly transparent about inputs and outputs.

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 clear opening sentence defining the tool, a paragraph explaining the musical concept and distinguishing from siblings, followed by a bulleted list of parameters. Every sentence adds value, and the most important information is 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 tool's complexity (10 parameters, no required fields, no enums) and that an output schema exists, the description is complete. It explains all parameters, provides examples, and mentions return values. The only minor gap is potential side effects, but the output schema covers return info.

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 description adds significant meaning beyond the input schema (which has 0% coverage). Each parameter is explained with ranges, defaults, examples, and constraints (e.g., 'transposition must have exactly voices values'). This fully compensates for the schema's lack of 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 clearly defines the tool's purpose: 'Create a canon — strict melodic imitation with delayed voice entries.' It specifies the verb 'create' and the resource 'canon', and distinguishes from sibling tool 'create_counterpoint', which generates a new independent melody rather than copying the same melody.

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 explicit guidance on when to use this tool (to create a canon) and when not to (for generating new independent counterpoint). It directly contrasts with 'create_counterpoint' and gives real-world examples like Pachelbel's Canon and 'Row Row Row Your Boat' to clarify usage context.

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