remove_clip

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

With no annotations provided, the description carries full responsibility for disclosing side effects. It explicitly warns that the operation is destructive and details what ripple does (closes gap, shifts content) versus lift (leaves a gap).

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 extremely compact—two sentences that front-load the core purpose, then clarify behavior and provide a safety reminder. 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?

For a destructive edit tool, it covers the essential aspects: what it does, how each mode behaves, the safety caveat, and a recommended workflow (verify with get_timeline). No output schema is needed for a removal action.

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 covers both parameters with descriptions, so baseline is 3. The description adds meaningful behavioral context to the 'ripple' parameter by explaining its effect on the timeline, and underscores the importance of node_id with the destructive warning.

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?

Clearly states 'Remove a clip from the timeline' with a specific verb and resource. The ripple vs. lift distinction further differentiates it from sibling tools like move_clip or trim_clip.

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?

Directs the user to confirm the node ID with get_timeline first, naming a specific alternative tool for verification. It also explains the two operational modes (ripple vs. lift), clarifying when to choose each behavior.

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