delete_clip

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

With no annotations, the description must carry the full burden. It only says 'Delete a clip', which implies destruction, but omits details like whether deletion is permanent, if the clip must exist, or what happens during playback. No additional behavioral context is provided.

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 very concise: two sentences plus a parameter list. The main action is stated first, and the parameter list is clear. No wasted words.

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 the tool's simplicity (2 parameters) and the presence of an output schema (not shown), the description covers the essential action. However, it lacks context on error cases (e.g., clip not found), side effects, or prerequisites, leaving some gaps for a complete understanding.

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 has 0% description coverage, so the description fully explains the parameters. It specifies that both indices are 0-based and clearly associates track_index with track number and clip_index with clip slot, adding meaning beyond the raw schema.

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 'Delete' and resource 'clip from a clip slot'. It distinguishes itself from sibling tools like stop_clip, fire_clip, create_clip, etc., which perform different clip operations.

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 only states what the tool does but provides no guidance on when to use it versus alternatives (e.g., stop_clip, duplicate_clip_to). No explicit when-not or contextual clues are given.

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