mcp_opendaw_create_clave

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

With no annotations, the description carries the burden of transparency and delivers detailed behavioral information: exact beat positions for each clave type, return values, and parameter meanings. However, it does not disclose potential side effects like whether existing notes are overwritten or how the pattern interacts with the target track.

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, front-loaded with a clear purpose, and uses bullet lists and examples effectively. It is somewhat long and includes minor redundancy (e.g., all bars defaults are 2), but every section adds 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?

The description covers the core concept and most parameters, and the output schema handles return values. However, it misses start_beat and unit_index semantics, and does not explain how the pattern is placed in the project or whether it clears existing notes, which is a notable gap for a complex tool.

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 description richly explains clave_type with beat mappings for all six variants, and gives meaning to bars, pitch, velocity, and duration. However, start_beat and unit_index are not described, and track_index only appears in examples, leaving a few parameters without semantic coverage.

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 it creates an Afro-Cuban clave pattern and explains it is a timeline pattern, not a drum pattern. This gives a specific verb+resource, but it does not explicitly distinguish itself from sibling tools like create_tumbao or create_drum_pattern beyond the musical concept.

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 provides strong musical context, explaining that the clave is the rhythmic skeleton all other rhythms align to and that every Afro-Cuban rhythm has a direction. This implies when to use the tool, but it does not explicitly state when not to use it or name alternatives.

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