browser_storage_load

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

With no annotations, the description carries the full behavioral burden. It does disclose the important side effect that localStorage restore navigates to each origin, which is valuable. However, it does not state whether existing cookies/localStorage are overwritten, how failures are reported, or whether a page must be active.

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?

Three short sentences each carry distinct information: the action, the input options, and a key side effect. It is front-loaded and free of fluff.

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?

The core invocation details and one major side effect are present, but there is no mention of return values, error handling, or how the restored state interacts with the existing browser session. Given no output schema and no annotations, this leaves meaningful gaps for an agent.

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% for both parameters, so the schema already documents path and state. The description largely restates that you can provide a file path or inline object without adding new parameter-level details beyond the schema baseline.

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 uses a specific verb ('Restore'), names the resource ('session from a storageState'), and clarifies what storageState contains (cookies + localStorage). This clearly differentiates it from siblings like browser_storage_save and the granular cookie/localStorage tools.

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?

There is no guidance about when to use this tool versus browser_storage_save, cookie_set, or localstorage_set, and no mention of scenarios where using it would be inappropriate. It only explains how to provide input, not when to choose this tool.

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