slip_edit

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

With no annotations provided, the description carries the full behavioral disclosure burden. It fails to state whether slip_edit modifies the selected clip, shifts media content in/out, affects edit points, or returns any feedback. The agent gets no observable behavior information.

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 extremely short and front-loaded, but brevity here is under-specification rather than effective conciseness. The phrase adds little beyond the tool name and does not earn its place as a useful operational definition.

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 tool in a large sibling family with no output schema and no annotations, the description is severely incomplete. It omits the required editing context, selection requirements, timeline impact, return value, and any distinction from roll_edit or slide_edit.

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 schema defines zero parameters, so there are no parameter semantics for the description to explain; the baseline 4 applies. The description adds nothing about arguments, but no required parameters exist to compensate for.

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: slip edit' mostly restates the tool name and adds only a broad category label. It does not explain what a slip edit does or what resource/state it acts upon, so an agent cannot derive the actual purpose beyond the name.

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 slip_edit versus alternatives like roll_edit or slide_edit. The description does not mention required preconditions such as an active sequence, a selected clip, or an edit point.

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