mcp_opendaw_create_drum_fill

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

No annotations are provided, so the description carries the full burden. It mentions that the tool 'Generates rhythmic fills... with increasing/decreasing density' and lists fill types with behaviors (e.g., 'build' increases density). It also explains the unit_index default. However, it does not disclose whether existing notes are overwritten or if the tool is purely additive, leaving some ambiguity about side effects.

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 a clear opening, a separate list of fill types, and parameter explanations. It is informative without being overly verbose, though some information (like the bar breakdown) could be integrated more efficiently.

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?

The description covers the tool's purpose, parameter details, and return value ('Returns notes created per lane and total'). However, it lacks explicit prerequisites (e.g., requiring a drum track or empty note area) and does not fully specify behavior when the target track already contains notes. Given the output schema exists, the description is largely complete but could add more context about the required state of the project.

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 has 0% description coverage (only titles), so the description fully compensates by explaining each parameter: fill_type with enumerated options, bars (1-4, each bar = 4 beats = 16 steps), start_beat, density (sparse/medium/dense), unit_index (default -1 finds first AU with note tracks). This provides complete semantic meaning beyond the 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 clearly states 'Create a drum fill or transition pattern' with a specific verb (create) and resource. It explains that one call replaces 10-30 note creations and provides fill types. This distinguishes it from sibling tools like create_drum_pattern and create_break by focusing on fills and transitions.

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 gives explicit use cases: 'Useful for transitions: verse→chorus, breakdown→drop, outro buildup.' This provides clear context for when to use the tool. However, it does not explicitly state when not to use it or compare to alternatives like create_drum_pattern.

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