mcp_opendaw_create_breakbeat

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

With no annotations, the description carries the full burden. It transparently discloses the musical behavior, including per-subtype note placements and velocity adjustments. However, it is silent on placement mechanics (track_index, start_beat) and whether existing notes are overwritten or added, leaving uncertainty 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 lead, bullet-like breakbeat_type details, parameter explanations, and an example. It is long but each section serves a purpose; the historical context, while informative, could be trimmed slightly. Overall, it is a high-value description that 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?

The core creation behavior and musical content are thoroughly covered, and the output schema covers return values. However, key parameters like start_beat and unit_index are not explained, and there is no mention of how the pattern integrates into an existing project (e.g., whether it overwrites a region). These gaps make the description incomplete for a tool with 10 parameters and no annotation support.

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?

Since the schema has 0% description coverage, the description compensates well for most parameters: breakbeat_type values are exhaustively detailed, and bars, pitches, and velocity are explained with defaults. However, start_beat and unit_index are entirely undocumented, and track_index only appears in the example without semantic explanation, leaving some parameters underspecified.

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 purpose: 'Create a breakbeat pattern' and elaborates on specific subtypes (amen, dnb, big_beat, etc.). However, it does not explicitly distinguish itself from sibling tools like create_drum_fill or create_break, so it falls short of the highest score for sibling differentiation.

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 strong contextual guidance on when each breakbeat_type is appropriate, linking them to genres and artists (e.g., 'The DNA of jungle and DnB'). It does not provide explicit exclusions or alternatives, but the context is clear enough for an agent to decide when to use this tool.

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