slide_edit

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

No annotations are provided, so the description must disclose behavior. It provides zero information about what the operation changes, whether it modifies clips, selection requirements, or side effects. The description is effectively empty of behavioral detail.

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 under-specified. It is a single sentence, but it does not earn its place because it provides no meaningful information. This is not concise writing; it is a placeholder.

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?

Given the tool's complexity and the lack of annotations, output schema, and meaningful description, the entire context is missing. The agent cannot infer what slide_edit does, what inputs it expects, or what effects it has on the timeline.

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 parameters, so the baseline is 4. There is no parameter information needed, and the description does not need to explain parameters beyond what the schema already indicates.

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' merely restates the tool name without defining what a slide edit does. It provides no verb or resource beyond the name itself, and fails to distinguish from sibling tools like roll_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?

No guidance is given on when to use this tool or how it differs from alternatives. With many similar timeline editing tools (roll_edit, slip_edit, ripple_delete), the description offers no context for selection.

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