Import Storage State

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

The description discloses that the action clears and replaces cookies, localStorage, and IndexedDB, and can overwrite a real logged-in profile. This goes beyond the annotations (destructiveHint=true) by detailing exactly what is destroyed.

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 concise sentences: first states purpose and when to use, second lists preconditions, third gives next step and sensitivity. No irrelevant information.

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 destructive nature and the presence of an output schema (so return values need not be explained), the description covers preconditions, behavioral effects, and next steps adequately.

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?

With 0% schema description coverage, the description compensates by explaining the purpose of the acknowledgment parameters (raw-capture, credential, overwrite). The 'path' parameter is implied but not explicitly described; still, it adds significant meaning 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?

Description clearly states the tool replaces active browser credentials and origin state from a Playwright storageState file, with a specific verb ('import') and resource ('storage state'). It distinguishes this from siblings like browser_export_storage_state.

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?

Description provides explicit preconditions (acknowledgments required) and a next step (navigate/reload). It does not explicitly list alternatives or when not to use, but the specific context ('full-profile authorized reproduction') implies narrow usage.

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