browser_restore_storage_state

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

With no annotations, the description carries full responsibility for disclosing behavior. It fails to mention that restoring state likely overwrites current storage, requires a previously captured state, or has other side effects. The description is behaviorally opaque.

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 a single short phrase, but this is under-specification rather than conciseness. It omits essential information that would make the tool usable.

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 likely side effects, a parameter, and no annotations/output schema, the description is severely incomplete. It should explain what 'restore' means, how to obtain a valid state, and what happens to current browser state.

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 lists a required 'state' object parameter with no description. The tool description does not compensate; schema coverage is 0% and the description gives no hint about the expected structure or contents of the state object.

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 '恢复存储状态' (restore storage state) is a direct translation of the tool name, providing no additional specificity. It does not distinguish this tool from siblings like browser_storage_state or browser_set_local_storage, nor does it clarify what 'storage state' includes (cookies, localStorage, etc.).

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?

There is no guidance on when to use this tool versus alternatives such as browser_set_local_storage or browser_storage_state. No context, prerequisites, or exclusions are provided.

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