slide_edit

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

Annotations indicate non-readonly and non-destructive. The description adds that adjacent clips are adjusted (ripple effect), which is useful. However, it lacks details on side effects like track locks or undo behavior beyond annotations.

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?

The description is succinct with two sentences. The first sentence conveys purpose and key behavior. The second sentence ('Uses QE DOM') while technically accurate, may be unnecessary for most agents, but overall the description is well-structured and to the point.

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 the tool has only two parameters with full schema coverage and no output schema, the description covers the core functionality. However, it lacks context on error handling, track constraints, and precise behavior when adjacent clips cannot be adjusted (e.g., at timeline bounds). This limits completeness for selection among similar sibling tools.

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?

Both parameters are fully described in the schema (100% coverage) with type and meaning. The description adds no additional semantic value beyond what the schema already provides, such as units or constraints.

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 states it performs a 'slide edit' that moves a clip without changing its duration and adjusts adjacent clips. This distinguishes it from general move_clip or trim tools. However, it doesn't explicitly differentiate from similar edits like slip_edit or roll_edit.

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?

No guidance on when to use this tool versus alternatives such as slip_edit, roll_edit, or move_clip. The description does not mention prerequisites, track requirements, or scenarios where this edit is appropriate.

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