slide_edit

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

With no annotations provided, the description must carry the full burden. It mentions using QE DOM and adjusting adjacent clips, but it does not disclose potential side effects (e.g., behavior at timeline boundaries, undo behavior, constraints on offset). This leaves some ambiguity for an AI agent.

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 two sentences, front-loading the purpose and adding only one additional piece of information (uses QE DOM). Every sentence adds value; no redundancy.

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 tool with 2 parameters and no output schema or annotations, the description covers the core behavior but lacks details on constraints, failure modes, or expected outcomes in edge cases. It is adequate but not fully comprehensive.

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 input schema already provides descriptions for both parameters (node_id, offset_seconds) with clear semantics. The description adds no extra parameter information beyond what the schema offers. With 100% schema coverage, baseline 3 is appropriate.

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 the action (slide edit), the resource (clip), and distinguishes it by noting it moves the clip without changing duration and adjusts adjacent clips. This differentiates it from siblings like move_clip, ripple_delete, slip_edit, and 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?

The description implies usage by explaining the effect (moves clip without duration change, adjusting adjacent clips), which helps the agent understand when to use it. However, it does not explicitly mention when not to use it or name direct alternatives.

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