delete_clip

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

With no annotations, the description carries the full burden and does well by disclosing the destructive side effect ('deletes a clip in one Live undo step') and an edge case ('empty slots return BAD_INPUT'). It doesn't cover whether permissions are needed or whether associated data is removed, but the core behavioral traits are present.

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 three compact sentences, front-loading the core action and then adding side effects and edge cases. No wasted words, though the example sentence could be slightly more informative.

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?

For a simple delete tool with no annotations and no output schema, the description covers the action, side effects, and an error condition. However, it leaves a significant gap in parameter semantics and does not explain return values or any prerequisites, so it is adequate but not complete.

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 provides only an example ('delete_clip(0, 1) removes the clip in slot one') without explaining what track_index and clip_index mean, whether indexing is 0-based or 1-based, or how the parameters relate to Ableton's track/slot model.

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 ('Delete') and resource ('Session clip slot'), making it clear that this operates on session clips rather than arrangement clips. However, it does not explicitly name the sibling 'delete_arrangement_clip' to sharpen the distinction.

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?

Usage is implied by the operation itself, and the edge case note about empty slots returning BAD_INPUT gives a constraint. But there is no explicit guidance on when to choose this tool over alternatives like clear_clip_notes or delete_arrangement_clip.

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