wp_rollback_snapshot

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses the key safety default (new copy) and that overwrite requires opt-in, which is valuable, but omits permissions, reversibility, and side effects of restoring, leaving significant behavioral gaps.

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?

Single front-loaded sentence with no filler; it efficiently conveys the core action and default behavior. However, the brevity contributes to parameter and behavioral gaps, so it is not maximally helpful.

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?

With no annotations, 0% schema coverage, and a mutation action, the description should do more. It does not cover the required snapshot_id, optional output_path, permissions, or side effects. Output schema exists, so return values needn't be explained, but the description remains incomplete for safe invocation.

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 0%, so the description must compensate for all three parameters. It alludes to overwrite_original ('original overwrite requires explicit opt-in') and default output ('new .world copy'), but never names or explains snapshot_id or output_path, and gives no format or type details.

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 ('Restore') and resource ('snapshot') and includes default output behavior. It does not explicitly differentiate from siblings like wp_list_snapshots or wp_apply_terrain_plan, but the restore action is distinct enough for an agent to identify.

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?

Provides conditional guidance: default creates a new .world copy, and overwrite requires explicit opt-in. It does not state when to use this tool versus listing snapshots or other terrain tools, so usage is implied rather than explicit.

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