slip_edit

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

With no annotations, the description must disclose all behavioral traits. It provides none: no effects of the operation, no requirements (like a selected clip), no whether it is destructive or reversible, and no return values. The user/agent is left completely in the dark about what happens when this tool is invoked.

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, but this is under-specification rather than conciseness. It consists of a single phrase that adds little value beyond the tool name. It lacks structure and substance, failing to earn its place as a useful description.

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 has no annotations, no output schema, and a sparse schema, the description is the sole source of context. It completely fails to explain the operation, its purpose, prerequisites, or effects. This is inadequate even for a low-complexity tool.

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 zero parameters, so the schema provides no info to describe. The baseline for 0 params is 4, and the description does not contradict or mislead. However, it also does not clarify the implicit input (likely the currently selected clip), but per the rule, the baseline stands without a reason to lower.

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 the operation is a slip edit in Premiere Pro, which is a specific editing action. However, 'expanded operation' is vague, and it mostly restates the tool name without explaining what slip edit does. It distinguishes from siblings like roll_edit by naming the specific operation, but the clarity is limited.

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. There are sibling tools like roll_edit and slide_edit, but the description gives no context about which situation calls for a slip edit or any prerequisites (e.g., selected clip). This is a fundamental omission.

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