piano_roll_add_chord

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

With no annotations provided, the description carries the full burden of disclosing behavioral impact, but it only says 'add a chord.' It does not mention whether existing notes are preserved, how velocity and duration defaults apply, which channel/piano roll is targeted, or whether the operation is reversible.

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 very short and front-loaded, but it achieves this by omitting essential behavioral and parameter information. It is concise without being adequately informative, so it sits at the minimum viable level.

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 four parameters, no output schema, and no annotations, the description is far too incomplete for an agent to invoke the tool correctly. The required midi_notes parameter is entirely unexplained, and the relationship to the active piano roll context is absent.

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%, and the description adds no explanation of the parameters. It does not clarify that midi_notes defines the chord tones, what time_bars means, how duration_bars behaves, or what velocity default 0.8 implies.

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 states a specific verb ('Add') and resource ('chord') and indicates placement at a bar position, which distinguishes it from generic piano_roll tools. It doesn't explicitly contrast with siblings like piano_roll_add_notes or piano_roll_add_arpeggio, but the chord focus is reasonably clear.

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?

No guidance is provided on when to use this tool versus alternatives such as piano_roll_add_notes or piano_roll_add_arpeggio. There is no mention of prerequisites like selecting a channel or opening the piano roll, nor any exclusion criteria.

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