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

Beyond the destructiveHint annotation, the description discloses important behavior: content after the extracted range is shifted left and sync-locked tracks follow. It does not mention reversibility or undo, but the core ripple effect is made explicit.

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 concise sentences with the operational behavior front-loaded and a short use-case sentence afterward. There is no redundant or wasted text.

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 editing operation with annotations and a fully documented schema, the description provides enough behavioral context about the ripple effect. It does not cover return values, but there is no output schema and that is not required here.

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 100%, so the parameters are already well documented. The description reinforces the half-open range semantics and track scoping, but adds limited parameter-specific detail beyond 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?

The description states a specific operation: extracting a half-open frame range on one track and shifting later content left to close the gap. It clearly describes ripple-delete behavior, though it does not explicitly name or contrast sibling tools such as remove_clips or trim_clips.

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 gives clear usage context: 'tightening a cut or removing a bad take.' This helps an agent understand the intended scenario, but it does not state when not to use it or name specific alternatives for non-ripple deletion.

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