gen_emit_arpeggio

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

No annotations are present, and the description does not disclose side effects (e.g., whether existing notes are cleared, if the action is reversible, or system requirements). The presence of a 'clear_first' parameter hints at destructive behavior, but this is not explained.

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 single-sentence description is concise but lacks necessary detail for a tool with 10 parameters. It is front-loaded but insufficient.

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 high parameter count and lack of annotations or output schema, the description is severely incomplete. It does not explain the chord format, velocity, duration, or pattern, leaving the agent unprepared 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?

With 0% schema description coverage, the description adds no meaning to any of the 10 parameters. It mentions 'N octaves' but does not link to the 'octaves' parameter or explain other key parameters like 'root', 'quality', 'direction', or 'pattern'.

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 emits an arpeggio across N octaves for a given chord, which distinguishes it from other emit tools like gen_emit_bassline or gen_emit_melody.

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 like piano_roll_add_arpeggio or other gen_emit tools. The description gives no context for tool selection.

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