mcp_opendaw_create_montuno

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

No annotations are present, so the description must disclose behavioral traits. It provides extensive musical theory and parameter explanations, but it does not describe the tool's operational behavior in the DAW: whether it creates a new note region or appends to an existing one, whether it overwrites notes, or what side effects it has on the track. The description even says 'Returns notes created, chord progression, and pattern info' but does not explain how the notes are placed or if any destructive action occurs. This is a significant transparency gap for a creation tool.

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 clear sections: definition, differentiation, pattern types, rhythm options, and args. It is longer than average, but that is justified for a complex musical generation tool with 12 parameters. The front-loaded definition and contrast help quickly orient the reader. Some repetition of musical concepts could be tightened, but overall it earns its length.

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 (12 params, no annotations, 0% schema coverage), the description does a good job covering parameter semantics and musical context. However, it lacks operational completeness: it does not explain DAW-level behavior such as which track/unit the pattern is written to, whether it is additive, or how start_beat interacts with the existing timeline. The output schema exists, so return values are not fully needed, but the missing behavioral context prevents a higher score.

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 provides no parameter descriptions (0% coverage), so the description's 'Args:' section is the only documentation for all 12 parameters. It explains each parameter's purpose, with examples for chord_prog and clear definitions for pattern and rhythm values. This fully compensates for the schema's lack of textual descriptions and adds meaning beyond types/defaults.

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 the tool's function: 'Create a montuno — a repeating Latin/jazz piano ostinato pattern.' It distinguishes this from related concepts like arpeggiators and ostinato patterns, making the purpose specific and well-scoped. The tool name 'create_montuno' is also descriptive, but the description adds real semantic content beyond the name.

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 explicitly contrasts with arpeggiators and ostinato patterns: 'Unlike arpeggiators... or ostinato patterns... a montuno combines...' This gives clear guidance on when to choose a montuno over those alternatives. However, it does not name sibling tools like mcp_opendaw_create_ostinato or mcp_opendaw_create_arpeggio directly, nor does it discuss scenarios where another pattern generator would be preferred. The pattern and rhythm enumeration also gives context for selecting variants, but no explicit 'when-not to use' is stated.

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