midi_notes_clear

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Remove all notes' implies a destructive operation, but it does not state whether the action is reversible (e.g., via undo), whether it affects other clip properties, or what happens if the clip does not exist. For a destructive tool, this is a significant omission.

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 sentence with no fluff, front-loaded with the action. It is maximally concise and well-structured for a tool that performs a single, simple operation.

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?

While the operation is simple, the description lacks critical context for an agent to invoke it safely. It does not mention error handling, reversibility, or what the tool returns. For a destructive operation with no annotations and no output schema, the description should provide at least a warning about its destructive nature and any assumptions about the clip.

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?

The schema provides no description for the clip_id parameter (coverage 0%), so the description must compensate. It does not explain what clip_id refers to, how to obtain it, or any format constraints. The parameter name gives a basic hint, but no concrete semantics are provided, leaving the agent to infer its meaning.

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 clear verb 'Remove' and a specific resource 'all notes from a MIDI clip'. It unambiguously distinguishes itself from sibling tools like midi_notes_add (which adds notes) and midi_clip_quantize (which adjusts timing). An agent can immediately understand the operation.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention any prerequisites (e.g., clip must exist) or contrast with midi_notes_add, which might be used to edit notes incrementally. The usage context is only implied by the name and description.

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