mcp_opendaw_create_stab

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

With no annotations, the description discloses key behaviors: how rhythm characters are interpreted ('x' triggers a stab, '.' is a ghost/light stab), how chords cycle, that velocity is halved for ghosts, and that it returns notes, voicings, and rhythm hits. It stops short of detailing edge cases or whether it overwrites existing notes, but covers the core behavior.

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 one-sentence summary, followed by use cases and parameter detail. Each sentence adds value; the parameter explanations are thorough. It's longer than average but justified for 9 parameters, though the genre list could be trimmed.

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 9-parameter tool with no annotations and 0% schema description coverage, the description covers all parameters, provides examples, and notes the return value. It's practical and complete for agent invocation, though it doesn't address error handling or invalid input behavior.

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%, yet the description explains every parameter with formats, examples, ranges, and defaults. For instance, chords includes root names and chord types, rhythm includes grid notation and examples, and octave/velocity/stab_duration have explicit ranges. This fully compensates for the sparse 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 opens with a specific verb+resource: 'Create rhythmic stabs — short chord jabs' and elaborates with 'Generates short chord hits on a rhythmic grid.' This clearly distinguishes it from sibling creation tools (e.g., create_chop, create_chorale) by focusing on stabs and their musical context.

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 'Perfect for' list gives explicit musical contexts (house/disco off-beat stabs, funk syncopation, garage/shuffle, filling gaps between melody notes), signaling when to use this tool. It doesn't explicitly name alternative tools, but the contexts are clear enough to guide selection.

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