insert_midi_notes

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the safety profile is covered. The description's one contribution beyond that is the phrase "one native note-diff undo command," which usefully signals that the whole batch commits atomically as a single undoable transaction. It says nothing about the 10000 limit's failure mode, whether re-running the same call duplicates notes, or what dry_run/confirm_delete do.

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?

A single front-loaded sentence with zero filler; the action and its limits come first. It is arguably over-compressed for a call with a nested ten-field request object, but nothing is padded or redundant.

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?

An output schema exists, so return values need no explanation, but the tool is a mutating batch operation with nested request fields and an explicit confirm_delete flag that the description never addresses. Given that complexity, one sentence covering atomicity leaves out the guidance an agent needs to invoke it safely and 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?

Schema description coverage is 0% and the description explains none of the fields: not dry_run, not confirm_delete, not expected_revision (an optimistic-concurrency token whose stale-revision behavior is critical), and not the track_id versus region_id distinction. The 10000 figure merely restates the maxItems constraint already in the schema, and only start_ticks carries any explanation at all, so the description fails to compensate for the coverage 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?

States a specific verb and resource ("Insert ... notes") and adds two distinguishing qualifiers: MIDI note data at the internal/API level and a hard cap of 10000 per call. It does not name or contrast with edit_midi_notes, delete_midi_notes, or list_midi_notes, so the reader must infer the boundary from the verb alone.

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?

There is no explicit statement of when to use this versus edit_midi_notes (for changing existing notes) or delete_midi_notes. The word "insert" implies additive creation, but there is no mention of prerequisites, whether notes may overlap existing ones, or whether region/track must exist and be selected.

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