remove_from_timeline

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

The description simply restates the action, adding no context beyond annotations (destructiveHint=true). It doesn't clarify what happens to the clip (e.g., deleted or just removed from timeline), the effect on tracks, or prerequisites like an active sequence.

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?

Single sentence, no fluff. Could be slightly expanded without losing conciseness, but it's efficient.

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?

No output schema, and the description omits important context like which timeline (active sequence?), whether the operation is undoable, or how to obtain node_id. Minimal for a destructive operation.

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 coverage is 100%, and schema descriptions for both parameters ('ripple' and 'node_id') are clear. The tool description adds no additional meaning, so baseline score applies.

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 ('Remove a clip') and the resource ('timeline'). It distinguishes from sibling tools like 'ripple_delete' by focusing on removal without specifying ripple behavior, but it's specific enough to identify the tool's function.

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 on when to use this tool versus alternatives like 'ripple_delete', 'extract_selection', or 'remove_selected_clips'. The agent must infer context from the name and schema.

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