Save browser state

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

The description claims the stateId is 'safe,' directly contradicting the annotations' destructiveHint=true. It does not disclose what destructive action might occur (e.g., overwriting existing state, clearing storage). This is a clear annotation contradiction and a significant transparency failure.

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?

The description is two sentences, immediately states the core action, and includes the critical usage condition. Every word contributes value with no redundancy.

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 description covers the tool's purpose and ideal usage, but omits important context such as what 'supported storage' includes, behavior when a stateId already exists, error conditions, and the destructive implications flagged by annotations. It is adequate but leaves gaps for a complex save/restore operation.

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 schema description coverage at 0%, the description adds valuable meaning by referring to 'explicitly addressed session' (mapping to sessionId) and 'logical stateId' (mapping to stateId). However, it does not provide detailed syntax, constraints, or potential values beyond what the schema's type and length limits already offer.

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 the specific verb 'Save' and clearly states the resource: 'cookies and supported storage from one explicitly addressed session under a safe logical stateId.' This distinguishes it from sibling tools like browser_state_list and browser_state_remove, which perform different actions.

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 provides explicit usage context: 'Use this only when a later new isolated session should restore that authentication state.' This clearly indicates when the tool should be used, and the 'only when' phrasing implies when not to use it, though no alternative tools are mentioned.

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