remove_clip_notes

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

With no annotations, the description carries the full burden. It discloses that the tool removes notes and defaults to removing all notes, but does not mention whether the operation is reversible, if it affects automation, or any permission requirements. The behavior is clear but lacks depth.

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 extremely concise with two sentences. The first sentence states the core purpose, and the second provides critical default behavior. Every word earns its place with no redundancy.

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?

Given 6 parameters, no schema descriptions, and no annotations, the description is minimal. It covers the core use case and default behavior, but does not explain parameter ranges, error conditions, or return values. The output schema exists but isn't leveraged for additional context.

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 mentions 'pitch/time range' but does not explain the specific parameters (time_start, time_span, pitch_start, pitch_span), their units, or how the defaults work. The description adds minimal value to understanding the parameters.

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 ('Remove MIDI notes'), the resource ('clip'), and the scope ('within a pitch/time range'). It also explicitly mentions the default behavior ('removes ALL notes') and how to target specific notes, which distinguishes it from sibling tools like add_clip_notes and set_clip_notes.

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 provides basic guidance on usage ('Specify ranges to target specific notes') and implies when to use ranges, but it does not explicitly state when to prefer this tool over alternatives like set_clip_notes or add_clip_notes, nor does it mention when not to use it (e.g., if you need to preserve notes).

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