mcp_opendaw_create_melodic_polyrhythm

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It explains that the tool creates notes that ascend or descend through a scale and provides parameter details like velocity patterns. However, it does not disclose side effects (e.g., whether it overwrites existing notes, if there are prerequisites for track_index, or what happens on error). It also doesn't mention the output schema, though one exists. The description is moderately transparent but could be more explicit about behavioral aspects beyond basic functionality.

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 lead sentence defining the purpose, a brief explanatory paragraph, and a clear parameter list. It is front-loaded with the core concept. While it includes some extra context (musical applications), every sentence adds value. It is not overly verbose given the complexity of the tool, but slightly longer than necessary. Score 4 for good structure and efficiency.

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 complexity (12 parameters, no annotations, has an output schema), the description covers the tool's purpose and parameter details well. However, it omits information about the return value (despite an output schema existing), error conditions, prerequisites for using the tool (e.g., track must exist), and idempotency. The musical context is useful but not essential for correct invocation. The description is adequate but incomplete for a fully autonomous agent.

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, and it does so effectively. Each parameter (12 total) is described in a separate line, explaining its purpose, allowed values, defaults, and format (e.g., 'pitches: Comma-separated MIDI pitches' and 'direction: Pitch direction when using scale generation — up/down/alternate'). This adds significant meaning beyond the bare schema. Minor gaps: 'velocity_pattern' enum values are listed but not enumerated in the schema; some defaults are repeated from schema but still helpful. Overall, the param descriptions are thorough.

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 polyrhythm — N notes evenly spaced across M beats.' It distinguishes this tool from the sibling 'create_polyrhythm' by specifying it creates a 'melodic polyrhythm rather than just rhythmic hits.' The verb 'create' combined with the resource 'melodic polyrhythm' and the specific explanation of cross-rhythms against a main pulse makes the purpose unambiguous.

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 context about when this tool is appropriate, mentioning jazz cross-rhythm, prog-rock metric modulation, etc. However, it does not explicitly tell the agent when to use this tool versus alternatives like the sibling 'create_polyrhythm' (which is a non-melodic version). No 'when not to use' guidance is given, so the agent must infer usage from context.

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