Undo changes in the last file edited or reverted.

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

Annotations declare destructiveHint=true. The description adds context about scope (last file edited before most recent mutating tool) and clarifies undo_file_edit is mutating. However, lacks details on what revert entails (e.g., state restoration) and any limitations.

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?

Description is one sentence, concise and front-loaded. However, the phrasing is slightly awkward ('on it(undo_file_edit is also mutating)'), slightly reducing clarity.

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?

Core behavior is described, but edge cases (e.g., no previous mutation, behavior after multiple mutations) are missing. Output schema may cover return values, but the description lacks completeness for usage.

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?

No parameters exist, so no parameter semantics are needed. The description correctly implies no arguments. With 100% schema coverage for 0 params, baseline 4 is appropriate.

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 that the tool reverts the last file edited before the most recent mutating tool, distinguishing it from siblings like undo_file_edit which is also mutating. The verb 'Revert' and resource 'last file edited' are specific.

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 explicit guidance on when to use this tool versus alternatives like undo_file_edit or revert_file. Only a hint that undo_file_edit is mutating, but no comparison or recommendation.

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