remove_selected_clips

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It states 'remove' but does not reveal whether the operation is destructive, ripple-deletes, removes from the timeline or project, or supports undo. The ambiguity is significant for a mutating operation.

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 short sentence and is front-loaded with the action, but the prefix 'Premiere Pro expanded operation' is boilerplate that adds no information. It is concise but contains a filler phrase that does not earn its place.

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 no output schema and no annotations, the description should clarify the scope of removal (e.g., timeline vs project, ripple vs non-ripple). It does not, and the presence of sibling tools with similar removal semantics makes this ambiguity problematic.

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 tool has zero parameters, and the input schema is empty. The baseline for 0 params is 4; the description adds no parameter details, but none are needed since no parameters exist.

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 uses a clear verb+resource construction ('remove selected clips') that states what the tool does. However, it does not distinguish this from sibling removal operations like lift_selection, extract_selection, or ripple_delete, and the phrase 'expanded operation' is generic.

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 about when to use this tool versus other removal or selection tools. There is no mention of context, prerequisites, or alternative tools, leaving the agent to infer usage from the name alone.

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