remove_span

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

With no annotations, the description discloses key behaviors: A-roll trimming, rest shifting, cached B-roll reuse, re-render, and streaming into the editor. It does not explicitly mention rollback or destructive warnings, but the 'cut out' language implies irreversibility.

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 pack the purpose, examples, and effects with no filler. The description is front-loaded and every clause adds value.

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?

Given low complexity, full schema coverage, and no output schema, the description covers purpose, behavior, and output effect ('streams into the editor'). It is sufficiently complete for an agent to select and invoke the tool correctly.

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 covers all parameters at 100%. The description adds meaning by showing [from_sec, to_sec] as a contiguous span and giving examples, while job_id is left to the schema's own description.

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 identifies a specific operation: removing an internal time span from a Swap & Refine video, with concrete examples. It distinguishes itself from edge-trimming by explaining the backbone A-roll is trimmed and the rest shifts up.

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 provides clear use cases ('duplicated opening sentence or dead pause'), indicating when removal is appropriate. It does not explicitly name alternatives like trim_clip, but the context is sufficient.

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