add_midi_notes_batch

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

The description adds the behavioral detail that timing is in beats (musical timing) and that the return is an object with a count of notes added. However, it does not disclose potential side effects such as whether existing notes are overwritten or if there are validation constraints. Since annotations only provide destructiveHint=false, the description adds some but not comprehensive behavioral context.

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 concise, with a clear one-sentence summary followed by structured Args and Returns sections. It is front-loaded with the main purpose and includes only necessary details, making it easy to scan.

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?

The description covers the essential information for calling the tool: the purpose, the structure of the notes list, and the return value. It does not explain error handling or edge cases, but these are not strictly required for a basic call. The description is sufficiently complete given the simplicity of the other parameters and the presence of only one complex parameter that is fully documented.

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?

The description provides detailed semantics for the notes parameter, explaining it as a list of dicts with keys pitch, velocity, start_beat, length_beats, and optional channel. This is essential because the input schema has 0% description coverage and the notes array has no item schema. The other two parameters (track_index, item_index) are self-explanatory from their names, so the description adequately compensates for the schema gap.

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 action (add), the resource (multiple MIDI notes to an item), and the key differentiator (batch operation in one call, using beats). It is specific and distinct from the singular add_midi_note sibling.

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?

The description implies usage for adding multiple notes at once, but it does not explicitly state when to use this tool versus alternatives like add_midi_note, nor does it mention any prerequisites or exclusions. The guidance is implied rather than explicit.

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