mcp_opendaw_create_two_hand_piano

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

With no annotations provided, the description carries the full burden. It discloses return values ('Returns notes created, left/right hand voicings, and chord count'), explains the structural pattern (left hand accompaniment, right hand melody), and notes subtle behaviors like 'left hand slightly quieter.' However, it does not explicitly state whether the operation overwrites existing notes or if prerequisites such as a valid note track are enforced beyond mentioning indices.

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 long but well-structured: a clear summary, followed by parameter details, and a return statement. Each sentence earns its place, especially the enumeration of hand patterns and octave explanations. It is slightly verbose but appropriate for a 13-parameter tool with zero schema help.

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 (13 parameters, 1 required, no schema descriptions), the description is remarkably complete: it addresses input, behavior, patterns, and output. It lacks explicit error handling or edge cases (e.g., what happens if melody_pitches is empty for right_hand='melody'), but the coverage is strong enough for an agent to invoke 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 is the sole source of parameter meaning. It compensates thoroughly by explaining every parameter in detail, including examples for chords, enumerating left_hand and right_hand options with descriptions, clarifying melody_pitches usage, and defining octave and rate semantics. This far exceeds baseline.

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 combination: 'Create a two-hand piano arrangement — left hand accompaniment + right hand melody.' It clearly distinguishes from siblings by explicitly contrasting with create_chord_progression and create_melody, making the tool's unique role evident.

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 gives explicit when-to-use guidance: 'Unlike create_chord_progression (block chords only) or create_melody (single line), this combines both hands into one coherent arrangement.' This directly tells the agent when this tool is appropriate versus alternatives, fulfilling the dimension fully.

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