mcp_opendaw_create_euclidean_rhythm

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

Since no annotations are provided, the description carries the full burden. It discloses key behaviors: it creates notes, returns a binary pattern and Euclidean notation, and applies velocity accents (+0.15 to first onsets). However, it does not explicitly mention potential side effects like whether it replaces existing notes or appends to a track, nor does it address permissions or reversibility.

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 and front-loaded with the core purpose, followed by useful musical examples, a clear parameter list, return values, and concrete usage examples. Every section earns its place and there is no fluff.

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 10-parameter tool with no annotations and an output schema, the description provides substantial context: algorithm explanation, typical patterns, parameter details, return information, and examples. The main gap is the three undocumented parameters (start_beat, unit_index, track_index), which are likely important for target placement.

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?

With 0% schema description coverage, this description compensates well by explaining onsets, steps, rotation, bars, pitch, velocity, duration, including ranges and constraints (e.g., 'steps must be >= onsets'). It misses start_beat, unit_index, and track_index, which are only shown in the schema, so it is not fully comprehensive.

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 clear, specific statement: 'Create a Euclidean rhythm — distributes k onsets across n steps as evenly as possible.' It also explains the algorithm and lists classic rhythms (E(3,8)=tresillo, E(7,16)=samba), which clearly differentiates it from sibling tools like create_drum_pattern or create_clave.

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 rich context about Euclidean rhythms and their musical uses, implying when to use this tool (e.g., for tresillo, samba, or bembé patterns). However, it does not explicitly state when not to use it or name alternatives among the many sibling tools, so it falls short of a 5.

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