close_gaps

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the sliding-left effect but does not explain scope (selected clips vs. entire track), default track behavior, whether the operation is undoable, or how it interacts with sync/linked clips.

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?

A single front-loaded sentence with no filler. Every word contributes to the stated effect.

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 simple two-parameter editing tool with no output schema, the description covers the core effect. However, it omits how trackType and trackIndex affect scope and what the default behavior is, which matters 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 description coverage is only 50%: trackIndex is documented, but trackType and its enum are undocumented. The description adds no parameter meaning at all, leaving trackType semantics to inference.

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 gives a specific verb and effect: removing empty space between clips by sliding them left. It clearly identifies the operation, though it does not distinguish it from adjacent editing siblings such as ripple_delete_range or move_clip.

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 implies the operation is for closing timeline gaps but gives no explicit guidance on when to use it versus alternatives, no prerequisites, and no exclusions. An agent must infer the appropriate context.

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