live12_clip_remove_notes

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

No annotations are provided, so the description carries the full burden of behavioral disclosure for a destructive mutation. It says notes are removed, but does not mention irreversibility, undo behavior, partial removal semantics, failure cases, or what is returned.

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 a single front-loaded sentence with specific terminology and no wasted text. It identifies the action, the target resource, and the two supported mechanisms immediately.

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 schema is fully documented and the description identifies both operation modes, which is enough to understand the tool at a high level. However, for a mutation tool with no annotations or output schema, it omits important details such as required parameter combinations for window removal and side-effect behavior.

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 100%, so baseline is 3, but the description adds useful grouping beyond individual property descriptions by framing note_ids as one removal strategy and beat/pitch window parameters as another. It still does not specify which window parameters must be combined for a valid window operation.

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 states a specific verb and resource: it removes MIDI notes from a Live 12 clip. It also identifies the two supported removal modes and underlying methods, which clearly distinguishes it from siblings like add_notes, modify_notes, and transform_midi.

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 two usage modes, by note IDs or by beat/pitch window, but does not explain when to choose one over the other or how these differ from modify_notes or transform_midi. The mode names provide some guidance, but alternatives and exclusions are left implicit.

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