mcp_opendaw_create_drum_pattern

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

With no annotations, the description must disclose behavior. It explains velocities, unit_index default behavior, and the return value. However, it does not state whether existing notes on the target unit are overwritten or deleted, nor does it describe error handling for invalid patterns or missing units. Some behavioral transparency is present, but key side effects are omitted.

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 front-loaded with a clear one-line purpose, followed by a structured breakdown of the pattern format, lanes, example, and parameter explanation. Each section contributes value; the example is somewhat long but enhances understanding. Well-organized and concise overall.

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 two-parameter tool with a complex input format, the description provides enough to construct a valid call: complete pattern syntax, target unit selection, and return value. It does not cover edge cases or failure modes, but the core usage is fully addressed given the output schema exists and the description mentions the return value.

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, and the description fully compensates. It defines the pattern JSON format in detail, including allowed step characters, velocity values, lane names, and provides an example. It also explains unit_index semantics with its -1 default. No ambiguity remains for either parameter.

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 specific verb and resource: 'Create a drum beat from compact step-sequencer notation.' It further distinguishes itself by noting 'one call replaces 10-20 note creations,' making it clear this tool is for efficient drum pattern creation rather than individual note placement or other rhythmic tools.

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 explains how to use the tool with pattern syntax and unit_index, and includes an example, but it does not explicitly state when to prefer this tool over alternatives like create_drum_fill or create_euclidean_rhythm. Usage context is implied rather than explicitly guided.

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