rollback_apply

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

It discloses key behaviors: re-entering auth/rate-limiting/validation, and appending a new log entry with 'rollback_of=index'. Given no annotations, this provides solid insight into side effects and security checks.

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 concise, using three sentences to convey purpose, behavior, and requirement without any unnecessary words.

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 simple 3-parameter tool with no output schema, the description covers the core action, re-dispatch behavior, and the confirm requirement. It lacks return value details but is otherwise complete.

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 coverage is 100%, and parameter descriptions are adequate. The description reinforces the need for 'confirm=true' but adds minimal new detail beyond the schema.

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 clearly states the tool executes the rollback plan for a specific action_log entry, distinguishing it from the related sibling tool 'rollback_plan_get' which retrieves plans without executing.

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 description specifies that 'confirm=true' is required for execution and explains the re-dispatch behavior, but does not explicitly mention prerequisites like having a rollback plan or when to prefer this over other tools.

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