remove_empty_tracks

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. "Delete" signals a mutation, but nothing is said about irreversibility, whether the operation is undoable, whether locked or targeted tracks are spared, or that it acts on the active sequence — all material facts for a destructive, parameterless tool.

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 seven-word sentence with the destructive action and the target set front-loaded. There is no filler, and nothing could be removed without losing meaning.

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 destructive, zero-parameter tool with no annotations and no output schema, the description omits the essential scope (active sequence), the flagged side effects on markers/clips, and whether the action is reversible. Given the absence of any structured safety metadata, this is a significant gap.

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 declares no parameters, so there is nothing for the description to clarify; the baseline for a zero-parameter tool applies. The one implicit "parameter" (the sequence acted on) is left unexplained, which is the only small deduction.

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?

Specific verb ("Delete") plus a precise resource scope ("all empty video and audio tracks") tells an agent exactly what the tool does. It does not, however, differentiate itself from the sibling remove_track, which operates on a single track — the plural/bulk behavior is implied by "all" but never contrasted with the singular alternative.

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?

The description states no conditions for use, no exclusions, and never names the alternative (remove_track) or prerequisites. Because there are zero parameters, the agent also cannot tell which sequence the cleanup applies to (presumably the active sequence), which is precisely the guidance a caller needs before invoking a bulk deletion.

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