browser_storage_state

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

With no annotations, the description carries the full burden. It discloses that the tool saves to a JSON file and returns the path. However, it does not mention whether it overwrites an existing file, any permission requirements, or if it clears storage before saving. This is a moderate gap in behavioral transparency.

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 action (save cookies + localStorage to JSON). Every sentence serves a purpose: the first describes the operation, the second explains reload and return value. No wasted words.

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 the tool's simplicity and presence of an output schema, the description covers the basic usage (save and reload). However, it lacks details on parameter behavior and interaction with sibling tools like browser_localstorage_* or browser_cookie_*. The description is adequate but not fully complete.

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 coverage is 0%, so the description must add meaning. It mentions 'path' indirectly (reload via storage_state=path) but does not explain the path parameter's purpose or behavior (e.g., if omitted, a path is generated). The session_id parameter is not mentioned at all. The description adds little value beyond the schema.

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 it saves cookies and localStorage to a JSON file, mentions reloading via browser_new_session, and specifies it returns the file path. This is a specific verb+resource combination that distinguishes it from sibling tools like individual cookie or localStorage commands.

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 explicitly tells when to use this tool (to persist browser state) and how to reload it via browser_new_session. However, it does not mention when not to use it or provide alternatives, though the context is still fairly clear.

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