Remove clips

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

With no annotations, the description carries the behavioral burden. It discloses that this is a destructive removal, that 'region' removes every placement, and that 'delete_region' additionally drops the region from the pool unless other clips use it. It does not cover permissions, reversibility, or error behavior.

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 tightly written sentences front-load the primary action and then pack in the mode distinction and the 'delete_region' caveat. Every clause conveys useful information with no 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?

For a 6-parameter destructive tool with no annotations and no output schema, the description covers the essential selection logic and the key side effect of 'delete_region'. It does not address edge cases such as no matching clip, multiple matches without 'track', or whether the operation is undoable.

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 meaning beyond the schema by explaining the position-vs-region choice, the need for 'track' when there is ambiguity across tracks, and the conditional effect of 'delete_region' when other clips still use the region.

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 states a specific verb and resource: it removes a clip. It also distinguishes the two removal modes (timeline position vs. named region) and clarifies the one-clip scope, so an agent can tell exactly what the tool does.

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 clearly explains the two usage modes: use 'at' to remove one clip, or 'region' to remove every placement. It also notes that ambiguity across tracks requires 'track'. However, it does not compare against sibling tools like move_clip or cleanup_regions.

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