Shift an edit point between two adjacent clips in Adobe Premiere Pro while preserving the sequence duration, adjusting where one clip ends and the next begins.
Premiere Pro expanded operation: roll edit.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.3.0-ibintec.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description discloses no behavioral traits. It does not mention whether the operation modifies source or sequence clips, whether it is destructive, or what the outcome of a roll edit is.
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, but its brevity is due to under-specification rather than effective conciseness. It provides no substantive information beyond the tool name.
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?
Without an output schema, annotations, or a substantive description, the tool is severely incomplete. The mechanics, prerequisites, and effects of a roll edit are entirely absent, making correct invocation impossible.
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 defines zero properties but allows arbitrary additional properties via additionalProperties. The description offers no insight into what parameters the tool expects, leaving the agent without any meaningful input guidance.
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 states 'Premiere Pro expanded operation: roll edit,' which essentially restates the tool name without explaining what a roll edit is or what the tool accomplishes. It fails to distinguish this from sibling tools like slide_edit or slip_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?
There is no guidance on when to use roll_edit versus alternative editing tools such as trim_clip, slide_edit, or slip_edit. No context or exclusion criteria is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.