undo_apply

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

The description discloses this is a WRITE operation with medium risk, explains it dispatches an inverse tool (audited separately), and covers dry_run preview and single-use tokens. It lacks detail on error handling but is otherwise transparent.

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 concise (5 sentences plus parameter bullets), front-loaded with a summary in brackets, and each sentence adds value without redundancy.

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?

The description covers purpose, behavior, and all parameters adequately for a tool with no output schema. Minor omission is error handling or invalid input behavior, but overall it is complete for typical use.

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?

With 0% schema coverage, the description fully documents all three parameters (undo_id, dry_run, target) with clear explanations, providing essential meaning beyond the bare 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 explicitly states the tool applies a recorded undo by dispatching its inverse tool, and it distinguishes from the sibling undo_list (which lists undos) by focusing on application.

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?

It mentions dry_run for preview and that a token can only be applied once, but does not explicitly state when not to use or list alternatives beyond the implicit pairing with undo_list.

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