Slides a clip and its adjacent neighbors along the timeline to adjust edit points without changing overall sequence duration. Use it to reposition a clip in Premiere Pro while preserving surrounding timing.
Premiere Pro expanded operation: slide edit.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With zero annotations, the description must disclose behavior, side effects, and requirements. 'Premiere Pro expanded operation: slide edit.' reveals nothing about what the tool does, what changes it makes to the timeline, whether it's destructive, or what state it operates on.
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 sentence and extremely concise. However, it's concise to the point of being underspecified rather than efficiently informative.
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?
Despite the tool having zero parameters and no output schema, the description provides no operational context. A slide edit in Premiere Pro involves moving a clip while maintaining sync with neighboring clips, trimming the edit point, and adjusting ripple behavior. None of this critical context is conveyed. Furthermore, there's no documentation of prerequisites like having a valid selection, sequence, or an established edit point. It's impossible for an agent to determine when to use this tool or what the expected outcome is from 'expanded operation' alone.
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 is completely unconstrained (additionalProperties allowed, no property definitions), so the description adds essentially no parameter guidance. There are no enumerated or documented parameters to clarify.
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 'Premiere Pro expanded operation: slide edit' identifies the general purpose (slide edit in Premiere Pro) but lacks specificity about what the tool actually does. It doesn't clarify the target (selected clips? playhead position?) or distinguish itself from related trim/edit tools like roll_edit or ripple_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?
No guidance is provided on when to use this tool versus alternatives like roll_edit, lift_selection, or trim_clip. The context of 'expanded operation' is vague and doesn't explain what selection or state is required before invoking.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.