delete_clip

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

With no annotations, the description must disclose behavioral traits on its own. It only says 'Delete a clip' without noting whether the operation is irreversible, whether it works in session or arrangement view, or whether it removes the entire clip slot. The parameter descriptions add indexing context but no deeper behavioral detail.

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 two sentences long: the first states the purpose, the second is a tight parameter list. Every word earns its place, and there is no fluff or repetition of the tool name.

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 operation with two parameters and no output schema, the description is mostly adequate but lacks crucial context such as reversibility, session vs arrangement behavior, or what happens if the clip slot is already empty. Given no annotations or output schema, a slightly richer description would improve completeness.

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 compensates by explaining both parameters: track_index is 'the index of the track containing the clip' and clip_index is 'the index of the clip slot containing the clip.' This adds meaning beyond bare integer types, though it omits zero/one-based indexing details.

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 'Delete a clip from a clip slot,' which is a specific verb+resource. It distinguishes from sibling delete tools like delete_track, delete_scene, and delete_device by targeting clips and their slots.

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 clear context that this tool is for deleting a clip from a clip slot, which implies when to use it. It does not explicitly exclude alternatives such as remove_notes, but the scope is unambiguous enough for a basic delete operation.

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