remove_from_timeline

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

With no annotations provided, the description carries the full burden. It adds a meaningful behavioral detail: if sequenceId is omitted, it searches the active sequence first, then all sequences. However, it does not mention destructive side effects, undo behavior, or any prerequisites beyond the sequenceId hint, which is a notable gap for a mutation tool.

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, front-loaded with the core action and followed by a targeted usage hint. Every word earns its place; no fluff or redundant information.

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?

The description is adequate for a simple three-parameter tool with no output schema. It covers the core operation, the tricky sequenceId case, and refers to the related tool list_sequence_tracks. While it doesn't mention side effects or undo, the schema handles parameter details, so the description is reasonably 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?

The schema already describes all three parameters (100% coverage), giving a baseline of 3. The description adds value beyond the schema by specifying when to use sequenceId in a concrete context (clip ID from list_sequence_tracks for a non-active sequence), which is not captured in the parameter description itself.

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 'Removes a clip from the timeline' with a specific verb and resource. The second sentence adds a scoping detail about sequenceId, distinguishing it from simpler removal tools like remove_selected_clips by indicating how to handle clips from non-active sequences.

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 a specific, useful guideline for when to pass sequenceId (when the clip ID came from list_sequence_tracks for a non-active sequence). However, it does not explicitly contrast this tool with alternatives like remove_selected_clips, lift_selection, or ripple_delete, leaving the choice among siblings implicit.

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