List Snapshots

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-derivable behavior: newest-first ordering, the fact that only snapshots created by this server prior to the agent's own edits are listed, and a 30-day retention window that tells the agent results may be incomplete for older content.

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?

Two short sentences, with the core verb+resource+ordering front-loaded and the retention caveat placed last. No filler or restatement of the title.

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 explained, and the description covers ordering, retention, and scope. The one remaining gap for a snapshot/versioning surface is routing relative to list_page_history, get_page_version, diff_page, and restore_snapshot.

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 description coverage is 100% — the 'page' parameter already documents accepted forms (id, slug id, URL) and 'limit' documents its default and bounds. The description adds no parameter-level detail beyond what the schema carries, so the baseline of 3 applies.

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 and resource ('List the snapshots of a page body') plus scope ('that this server saved before your own changes to it') and ordering ('newest first'). An agent can identify what it returns, though the description never distinguishes it from close siblings like list_page_history or get_page_version.

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?

Usage is only implied: the 'saved before your own changes' framing hints at pre-edit recovery scenarios, and a sibling named restore_snapshot suggests the workflow. There is no explicit 'use this when X, use list_page_history when Y' guidance or statement of prerequisites.

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