mcp_opendaw_create_breakbeat

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

With no annotations provided, the description carries full burden. It discloses that notes are created, returns notes created, breakbeat type, and stroke breakdown. It details pitch defaults, velocity adjustments per stroke, and examples. However, it does not mention whether it clears existing notes or requires a specific track state.

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 purpose, then provides musical context, type details, parameter explanations, and examples. While somewhat lengthy, the structure is logical. A minor reduction in historical detail could improve conciseness without losing value.

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 tool's complexity (10 params, no annotations, output schema exists), the description is comprehensive. It covers breakbeat types, pitches, velocity, and return values. Missing explicit mention of start_beat and unit_index slightly reduces completeness, but overall it is well-rounded.

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%, so the description must compensate. It thoroughly explains breakbeat_type with extensive details, describes pitch defaults, velocity behavior, and bars. Examples show track_index usage. However, parameters like start_beat and unit_index are not described, leaving some gaps.

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 breakbeat pattern' and specifies it's 'the syncopated skeleton of jungle, DnB, big beat, and breakbeat hardcore.' It distinguishes from sibling tools that create other patterns (e.g., create_boom_bap, create_four_on_floor) by focusing on breakbeats and listing detailed types.

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 what breakbeats are and when they are used (e.g., jungle, DnB, big beat). However, it does not explicitly state when not to use this tool or compare it to alternatives like create_drum_pattern or create_boom_bap. The guidance is implicit through the type descriptions.

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