remove_selected_clips

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

With no annotations, the description must fully disclose behavioral traits. It states 'Remove' (destructive action) but fails to clarify whether clips are permanently deleted or moved to trash, whether the action is undoable, or what happens if no clips are selected. The ripple parameter is described in the schema, but the description does not reinforce the default behavior (no ripple, leaves a gap). These gaps could lead to misuse.

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 a single, well-structured sentence that immediately conveys the tool's core function. It avoids redundancy and is front-loaded. However, a brief addition about the ripple parameter's default could improve clarity without harming conciseness.

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 optional parameter and no output schema, the description covers the basic action. However, it omits important context: prerequisites (clips must be selected), behavior on empty selection, and how it differs from closely related sibling tools. This limits an AI agent's ability to use it correctly without additional knowledge.

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 coverage is 100% (the only parameter 'ripple' has a clear description in the schema). The tool description adds no additional meaning beyond the schema, but the schema itself is sufficient. Baseline 3 is appropriate since the description does not compensate for any schema gaps.

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 ('Remove') and resource ('all currently selected clips from the timeline'), making the purpose easily understandable. However, it does not differentiate from similar sibling tools like 'ripple_delete' or 'remove_from_timeline', which could cause confusion for an AI agent selecting between them.

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 is provided on when to use this tool versus alternatives (e.g., 'ripple_delete' for closing gaps, 'lift_selection' for cutting without removing). The description does not mention prerequisites (clips must be selected) or when not to use it (e.g., if you want to preserve the gap). The ripple parameter is mentioned but not contextualized.

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