update_notes

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

With no annotations, the description explains the matching logic (pitch + start_time with tolerance) and that it doesn't clear/rewrite. It could mention what happens if no match is found or return structure.

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?

Front-loaded with key purpose and benefit, followed by matching logic and parameter details. No redundant sentences; efficient and well-structured.

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 main usage and parameter details. Output schema exists so return values are excluded. Missing edge cases but sufficient for typical use.

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 coverage is 0%, but the description provides detailed parameter explanations including the updates list structure, required fields, optional new_* fields, and tolerance default.

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 it surgically modifies existing notes in a MIDI clip without clearing/rewriting, and explicitly distinguishes from sibling tools like clear_clip_notes and add_notes_to_clip.

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?

It explicitly recommends this tool over clear_clip_notes + add_notes_to_clip, providing clear guidance on when to use it. However, it doesn't cover all alternative scenarios.

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