ripple_delete

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

The description provides a single behavioral detail ('Uses QE DOM') but omits crucial aspects like side effects (non-destructive? reversible?), error conditions, or what happens to other clips. With no annotations, the description should have been more comprehensive.

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?

Extremely concise (two sentences) and front-loaded. Every word is necessary and contributes to understanding. No 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 simple tool with one parameter and no output schema, the description is minimally adequate. However, it lacks behavioral details like return value or error handling, and no annotations compensate. Could be slightly better.

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?

Only one parameter (node_id) with a clear schema description. The tool description adds no further meaning beyond the schema. Since schema coverage is 100%, baseline is 3.

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 ('ripple delete'), the resource ('a clip'), and the effect ('removes clip and closes the gap'). It distinguishes from sibling tools like simple delete or removal by specifying the ripple behavior.

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 explicit guidance on when to use this tool versus alternatives (e.g., remove_selected_clips). The description implies a specific scenario (closing gap) but does not state when not to use it or mention alternative tools.

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