storage_state_load

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

With no annotations provided, the description carries the full disclosure burden and does reveal the core behavior (loads cookies + localStorage) plus a conditional effect (bypass CF/login on a fresh session). It does not disclose that loading overwrites the current session state, nor what happens on a missing or stale file, which are material for a restore operation.

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 with zero waste, front-loaded with action and resource, and the purpose clause ('Bypass CF/login if session is fresh') earns its place with both intent and a condition. No repetition of schema content.

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 2-param loader with no output schema, the combination of description and schema covers what is loaded, the source format, the intended use case, and the same-origin navigation requirement (via navigate_to's schema note). It omits return value and overwrite semantics, but those are minor gaps for a straightforward restore action.

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%, so path and navigate_to are already documented, setting the baseline at 3. The description adds minor context about the file's contents (cookies + localStorage) but no format, syntax, or lifecycle guidance beyond what the schema provides.

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 (Load) and resource (cookies + localStorage from a JSON file), and names the companion tool that produces the file (storage_state_save). The stated purpose (bypass CF/login) makes it easy to distinguish from siblings like cookie_import or localstorage_set without opening their schemas.

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?

Names the paired producer tool (storage_state_save) and gives a clear use condition ('Bypass CF/login if session is fresh'), which tells an agent when this restore path is effective. It stops short of 5 because it never explicitly contrasts alternatives such as cookie_import or auth_capture or states when not to use it.

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