remove_from_timeline

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

With no annotations, the description must carry the behavioral burden, and it only states the basic destructive action plus a sequenceId condition. It does not disclose side effects such as ripple or lift consequences, irreversibility, permissions, or behavior when the clip ID is not found.

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?

Two sentences with no filler: the core removal behavior is front-loaded, and the second sentence provides a single necessary condition. Every sentence earns its place.

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 schema fully documents all three parameters, so the missing return-value/output detail is less critical. The description covers the one non-obvious sequence condition, but the definition as a whole still lacks alternative-tool routing and side-effect context for a mutation 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%, so the baseline is 3. The description adds real value by linking sequenceId to list_sequence_tracks and non-active sequences, going beyond the schema's generic statement that it searches the active sequence first.

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: 'Removes a clip from the timeline,' naming the verb, resource, and location. It does not explicitly compare against remove_selected_clips or ripple_delete, but the non-active sequence caveat hints at the tool's distinctive ID-based behavior.

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?

It gives one concrete conditional—pass sequenceId when removing a clip from a non-active sequence whose ID came from list_sequence_tracks—which is useful for sequencing. However, it does not name alternatives or state when to prefer this tool over selection-based removal tools like remove_selected_clips.

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