Remove From Timeline

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds real substance: linked partners are removed by default, sync-locked tracks shift, and the non-obvious caveat that Premiere's own ripple flag is a no-op on current builds. This exceeds what the annotations convey, though it doesn't cover permissions or reversibility.

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 front-loaded sentences: the core action first, then the ripple/linked detail. Dense but each clause carries information; the parenthetical asides are informative rather than filler.

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?

With an output schema, full annotation coverage, and 100% parameter descriptions, the description only needs to add behavioral nuance, which it does well for the default and ripple paths. It is complete for correct invocation.

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, but the description adds meaning beyond the schema by explaining what ripple actually does (closes the gap via verified ripple delete) and why linked partners go with it (closing one side would desync). It omits allow_large_ripple/threshold, but those are documented in the 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?

States a specific verb+resource ('Remove a clip from the timeline') and immediately differentiates its behavior from the sibling ripple_delete by describing the default linked-partner removal and the ripple variant. An agent can tell exactly what this does and how it relates to the ripple tool without opening a schema.

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?

Explains the default behavior and the ripple:true alternative, and names ripple_delete as the equivalent ripple path. However it gives no explicit when-to-use/when-not guidance relative to other removal siblings (remove_selected_clips, lift_selection, extract_selection), so routing is implied rather than stated.

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