mcp_opendaw_create_chaconne

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

With no annotations provided, the description carries full burden for behavioral disclosure. It reveals concrete side effects: 'Creates bass on track_index, chord pads on track_index+1, variation on track_index+2.' It also documents variation style behavior. However, it does not state whether existing notes are overwritten or if tracks must pre-exist, leaving some side-effect ambiguity.

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 efficiently structured and front-loaded with the core definition. Each subsequent section (bass pattern, bass rhythm, chord pattern, variation styles, track placement) adds necessary usage detail without fluff. It is longer than average but earns its length given the tool's complexity.

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 (9 optional parameters, compositional form, multiple styles) and zero schema descriptions, the description is fairly complete: it covers form definition, differentiation, parameter formats, style meanings, and output track placement. It falls short only on a few parameter semantics (repeats, velocity, start_beat, unit_index) and does not mention prerequisites about existing tracks, but overall it provides enough for an agent to use the tool correctly.

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 explains bass_pattern format ('space-separated note names'), bass_rhythm ('space-separated durations in beats'), chord_pattern ('comma-separated chord names', supported chord types), variation_style options with brief descriptors, and track_index placement behavior. However, repeats, velocity, start_beat, and unit_index are not described, leaving gaps for 4 of 9 parameters.

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 specific verb and resource: 'Create a chaconne — repeating bass + chord progression + developing variations.' It clearly defines what a chaconne is and explicitly differentiates it from ground bass and passacaglia, which are sibling tools. This resolves ambiguity among similarly named compositional generators.

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 explicitly contrasts chaconne with ground bass ('bass only') and passacaglia ('bass + variations'), stating that chaconne repeats both bass AND chord progression. This gives direct when-to-use guidance relative to named alternatives, satisfying the 5-level criterion of explicit when/when-not/alternatives.

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