undo

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

With no annotations provided, the description carries the full burden, and it does disclose one genuinely non-obvious trait: undo granularity in Premiere does not map 1:1 to tool calls. It still omits whether undoing past the stack start errors or no-ops, whether the undo stack is bounded, and whether project state is written to disk.

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?

One sentence plus a clarifying parenthetical, front-loaded with the verb and resource. Nothing is padding.

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 mutation tool with no annotations and no output schema, the description should state the default step count, error/no-op behavior at the bottom of the stack, and whether the operation is recoverable via redo. It covers purpose and the granularity caveat but leaves the operational essentials to inference.

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?

Schema description coverage is 0% for the single `steps` parameter, and the description never names it, states that it defaults to 1, or explains what happens if omitted. The parenthetical about 'several undo steps' gestures at the concept but is ambiguous about whether it describes the `steps` parameter or Premiere's internal behavior.

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?

States a specific verb (Undo) and scoped resource (the last action(s) in Premiere Pro), which is immediately distinguishable from the `redo` sibling in the tool list. An agent knows exactly what this does without opening the schema.

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?

The parenthetical clarifies that one tool call may correspond to several undo steps, which is context an agent needs to decide how many steps to request. However, there is no explicit statement of when to use this versus `redo`, no recovery guidance, and no note on what happens when there is nothing left to undo.

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