wp_list_snapshots

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 does not state whether snapshots are read-only, whether listing has any side effects, how many results return, pagination, or ordering. The word 'safety' hints at purpose but conveys no operational behavior.

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?

A single efficient clause that states the action and filter in twelve words. Nothing extraneous, though the terseness leaves gaps that additional precise context could have filled.

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?

An output schema exists, so return values need not be described. For a no-annotation, zero-schema-coverage tool with a sibling that performs the actual rollback, the description is minimally adequate but does not connect listing to the rollback workflow or describe result ordering or scope.

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%, but there is only one optional parameter with a default of null. The description explains that world_path restricts results to one original .world path, which is the key semantic the schema lacks. However, it does not clarify format, matching behavior, or what happens when omitted beyond 'optional'.

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 (List) and resource (safety snapshots), and adds the optional filter scope. It does not differentiate itself from the sibling wp_rollback_snapshot, but the listing action is clear from the name and description alone.

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 optional 'original .world path' filter implies a use case (enumerate snapshots for one world), but there is no explicit when-to-use guidance, no mention of the relationship to wp_rollback_snapshot as a follow-up action, and no stated preconditions.

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