storage_state_save

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

No annotations are provided, so the description carries the full burden. It discloses the core behavior—persisting cookies and localStorage to a JSON file—but does not state whether an existing file is overwritten, whether parent directories are created, or whether the saved state covers all origins or only the current one.

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 no filler. The action is front-loaded, and the second sentence adds valuable usage context about reloading the state to skip login/CF.

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 one-parameter save operation, the description covers what is saved, where it goes, and how to restore it. No output schema is present, but an agent has everything needed to select and invoke the tool correctly.

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?

The schema already documents path with a concrete example and 100% coverage. The description adds no new parameter-level detail beyond confirming the tool writes to a JSON file, so the baseline score of 3 is 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 resource: save cookies + localStorage to a JSON file. This is clearly distinct from siblings like cookie_export or localstorage_get because it bundles both into a single reloadable file, and it names the matching storage_state_load counterpart.

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 description gives clear context for when to use it: before launching a fresh browser, so the saved state can skip login/CF. It names storage_state_load as the reload counterpart, but it does not explicitly say when not to use it or how it compares with alternatives like cookie_export_file or auth_capture.

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