ripple_delete

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

With no annotations, the description carries the full burden of behavioral disclosure. It fails to mention that ripple delete removes selected clips and closes the resulting gap, that it modifies the timeline, or that the action may be destructive. The phrase 'expanded operation' adds no behavioral substance and provides no warning about side effects.

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 short, but that shortness is under-specification rather than deliberate conciseness. It resembles a title or placeholder, and the phrase 'expanded operation' is vague filler. A single clear sentence defining ripple delete would be both concise and more useful.

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 an editing operation with side effects in a complex tool environment, the description omits critical context: selection requirements, effect on timeline gaps, target sequence, and undo behavior. There is no output schema, so the description should at least explain the operation's scope and consequences.

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 0 declared parameters, so the description does not need to explain parameter behavior. The baseline of 4 applies here, even though additionalProperties: true technically permits arbitrary extra fields without documentation.

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 is essentially a restatement of the tool name: 'Premiere Pro expanded operation: ripple delete.' It names the operation but does not state what it does, what it acts on, or how it differs from similar tools like remove_selected_clips, extract_selection, or lift_selection. An agent unfamiliar with Premiere Pro terminology cannot infer the action from this text.

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?

There is no guidance about when to use this tool versus alternatives. It does not mention that a selection is required, that it operates on the active sequence, or how it compares to remove_selected_clips or extract_selection. The description is a label rather than usage guidance.

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