insert_midi_notes

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

No annotations are provided, so the description carries the full burden. It discloses the coordinate system (quarter-notes relative to item start) and per-note defaults, which is genuinely useful. However, for a mutation tool it omits whether notes are appended or replace existing content, whether the item must be selected, and any error behavior.

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?

Two sentences, front-loaded with the action, followed by the precise note payload spec. No filler; every clause carries 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?

With no annotations and no output schema, the description is responsible for the full behavioral picture. It covers the hardest ambiguity (note coordinates and payload) but leaves gaps: index semantics for track/item, append-vs-replace behavior, and what the call returns. Adequate but not complete for a write tool.

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 must compensate and it largely does: it fully documents the notes array element shape (pitch range, start_qn, length_qn, velocity and channel defaults) that the schema leaves as an unspecified additionalProperties object. track_index and item_index are only implied by name and remain unexplained, which keeps this from a 5.

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?

Specific verb+resource: 'Insert MIDI notes into an existing MIDI item.' It is clearly distinguished from the sibling insert_midi_item (which creates the item itself) by the word 'notes' and the constraint 'existing MIDI item'. An agent can select this over its siblings without opening the schema.

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?

'Into an existing MIDI item' implies a prerequisite (the item must already exist), which is useful guidance. But there is no explicit when/when-not statement or direction to alternatives such as insert_midi_item or create_chord_progression. Usage is only implied.

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