edit_notes

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

Description discloses that only specified notes are modified (not full rewrite) and that remove matches by pitch+start, which adds value beyond annotations (destructiveHint=false). Does not cover atomicity or error cases.

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 concise sentences plus structured spec. No redundancy; every word 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?

Covers key parameters and behavioral nuance, but lacks prerequisites (e.g., requiring clip to exist or be selected) and does not mention return values (though output schema exists).

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?

With 0% schema description coverage, the description compensates by detailing expected structure for add and remove arrays (pitch, start_time, etc.). However, track_index and clip_index are left unexplained.

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?

Description clearly states verb 'edit' and resource 'notes in a MIDI clip', distinguishing from siblings like add_notes_to_clip and delete_clip by emphasizing subset without rewriting all.

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 partial edits via add/remove, but does not explicitly state when to use this tool over alternatives like add_notes_to_clip.

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