Navigate back to the previous page in Chrome and optionally return the page snapshot to confirm the result.
Go back to the previous page
| Name | Required | Description | Default |
|---|---|---|---|
| snapshot | No | Also return the page snapshot after the action (default: yes). Use it when you need to see the result right away. |
Changes observed during successful MCP inspections.
v0.4.0Input schema / properties / snapshotAdded value: +{
+ "description": "Also return the page snapshot after the action (default: yes). Use it when you need to see the result right away.",
+ "type": "boolean"
+}v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare this mutates browser state (readOnlyHint=false) and interacts with an open world. The description adds nothing behavioral — notably it omits what happens when there is no history entry to go back to, or whether the call waits for the page to load before returning.
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, front-loaded sentence with zero filler. Nothing in it is redundant or padding.
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?
For a simple one-parameter navigation tool with annotations covering the safety profile, the description is minimally viable but under-specified: it says nothing about failure when no prior page exists or about whether the resulting page state is returned.
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?
There is a single optional parameter with 100% schema description coverage, so the schema already explains the snapshot flag and its default. The description adds no parameter meaning, making the baseline 3 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 states a specific verb and effect ('Go back to the previous page'), which is unambiguous and clearly distinct from browser_go_forward or browser_navigate. It does not explicitly name those siblings, but the action itself is self-identifying.
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 purpose implies when to use it (after navigating forward), but there is no explicit guidance on when to prefer it over browser_navigate, browser_reload, or browser_go_forward, and no mention of prerequisites such as existing history.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.