restore_page_state

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

With no annotations, the description carries full burden. It lists behaviors: navigates to URL, restores storage, cookies, HTML, scroll position. However, it does not mention side effects (e.g., overwriting existing page state), failure cases, or authentication details (apiKey parameter).

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 sentences, front-loaded with the core action (restore page) followed by what is restored. No redundant information.

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?

Given complexity (nested snapshot, 3 params, no output schema), the description covers core functionality but omits failure behavior, prerequisites (must have captured snapshot earlier), and return value. TabId default is implied by schema but not explicitly stated in description.

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 descriptions cover all parameters (100% coverage). The tool description adds value by explaining what the snapshot object contains (storage, cookies, etc.), which is not detailed in the schema's nested property descriptions. tabId and apiKey are clearly described.

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 the tool restores a page from a previously captured snapshot, using the verb 'restore' and specifying the resource 'page state'. It distinguishes itself from sibling tools like snapshot_page_state (capture) and navigate_to_url (simple navigation).

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. It is implied that it should be used after capturing a snapshot with snapshot_page_state, but no mention of excluding usage when just navigating is needed.

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