mcp_opendaw_create_jazz_arrangement

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

With no annotations, the description carries the full burden. It discloses the musical content in detail (ride pattern, walking bass, comping, horn lead) and mentions 'Returns notes created per track and total.' However, it does not state whether existing notes on the target tracks are overwritten, appended, or if any other side effects occur, leaving operational behavior ambiguous.

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 sections and line breaks, but it is verbose. It repeatedly emphasizes the 'fundamentally different' and 'signature' jazz elements across multiple sentences (e.g., re-explaining triplet feel and ii-V-I harmony). Some educational content could be trimmed without losing invocation-relevant information.

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 an 11-parameter tool with no annotations, the description covers the core functionality and most parameters, plus a brief return-value note. However, it leaves out velocity and start_beat parameters, does not explain behavior with existing notes, and relies on an unseen output schema to clarify return structure. These gaps make it incomplete for fully autonomous use.

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 coverage is 0%, so the description must compensate. It explains most parameters with added meaning: bpm range (60-200), bars range (4-32), root note example (F for horns), octave example (F2=41), unit_index purpose, and the four track indices. However, it omits velocity and start_beat entirely, which are present in the schema with defaults but no descriptions.

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+resource+scope: 'Create a full jazz arrangement — swing drums + walking bass + comping piano + horn across 4 tracks.' It clearly distinguishes this from sibling genre arrangement tools by emphasizing jazz-specific elements like swing feel and ii-V-I harmony, and by naming the exact track roles.

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 states 'Jazz with swing feel and ii-V-I harmony — fundamentally different from all other arrangements' and later reiterates that swing 8ths and ii-V-I set jazz apart. This implies when to use this tool (when a jazz arrangement is needed) and contrasts it with other arrangements, though it does not name specific alternatives.

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