add_midi_notes_batch

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

With no annotations provided, the description carries the full behavioral burden. It does disclose the return value ('Object with count of notes added') and the note dict shape, which is genuinely useful, but it never states whether notes are appended versus replacing existing content, what happens on invalid pitch/channel values, or whether item/track must already exist.

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 definition is compact and front-loaded: the first sentence states the action and timing model, followed by clearly separated Args and Returns blocks. Nothing is padded, though the docstring-style formatting is slightly verbose relative to the amount of information conveyed.

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 output schema, the explicit Returns note is valuable, and the notes payload is well described. However, for a 3-required-parameter mutation tool with zero annotation coverage, the description leaves the indexing parameters and append-vs-replace semantics unexplained, so an agent could still call it incorrectly.

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. It does well for the notes array, enumerating keys (pitch, velocity, start_beat, length_beats, channel) and marking channel optional, but track_index and item_index receive no explanation at all despite being required, leaving half the parameter surface undocumented.

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 and resource ('Add multiple MIDI notes to an item') and the 'in one call' phrasing signals the batch nature, which meaningfully separates it from the singular sibling add_midi_note. It does not explicitly name that sibling, so differentiation is inferable rather than stated.

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?

Beyond the implied 'multiple' vs single-note distinction, there is no explicit when-to-use guidance or routing to alternatives like add_midi_note or add_midi_notes_batch's relationship to create_midi_item. The agent must infer that this is the bulk-insert path when many notes are needed.

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