mcp_opendaw_create_drum_pattern

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

No annotations are provided, so the description carries full burden. It discloses the step-sequencer notation format, default unit_index behavior, and return value (notes created per lane). However, it does not state whether it is destructive or additive, or prerequisites like needing a drum track.

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 an opening sentence, parameter details, notation legend, and example. It is front-loaded with purpose. Only minor redundancy (the example could be shorter).

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 creating a drum pattern, the description covers all essential aspects: input format, notation, unit_index, and output. The output schema exists and the description mentions return value sufficient for the agent to use 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?

Schema description coverage is 0%, but the description fully explains the pattern parameter (JSON object, lanes, step characters) and unit_index parameter (default -1, finds first AU with note tracks). This adds significant meaning beyond the input 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 uses a specific verb ('create') and resource ('drum pattern') with unique compact notation. It clearly states it replaces 10-20 note creations, distinguishing it from siblings like create_drum_fill or create_boom_bap.

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 implies usage for efficient drum pattern creation but does not explicitly state when to use this tool versus alternatives such as create_drum_fill or create_four_on_floor. No when-not or alternative guidance is given.

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