piano_roll_add_notes

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

No annotations provided, so description carries full burden. Discloses note format and conditional auto-open, but does not mention default behavior for clear_first (appending vs overwriting) or possible error conditions. Lacks some behavioral traits.

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?

Only ~100 words, front-loaded with purpose, followed by note format and usage conditions. No redundancy, every sentence adds value.

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?

No output schema or annotations. Description explains input format and prerequisites but omits return values, error handling, and overall behavior for all parameters. Adequate but not complete for a tool with 4 parameters and no structured metadata.

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%; description compensates by explaining notes array structure (midi, time_bars, duration_bars, velocity range 0..1, optional pan -1..1) and channel's role. However, parameters clear_first and pattern are not described in text.

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?

Clearly states 'Add notes to a channel's piano roll' with the key qualifier 'works WITHOUT MIDI'. Differentiates from other piano_roll_* tools by focusing on generic note addition, though could be more explicit about distinction from add_arpeggio and add_chord.

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?

Provides explicit conditional guidance: if channel given and TCP bridge online, auto-opens; otherwise details manual steps. Missing explicit when-not-to-use vs alternatives, but prerequisites are clear.

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