browser_get_storage_state

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

The description only says 'Return,' which aligns with the 'readOnlyHint' annotation but adds no additional behavioral details. It does not explain what is included in 'storage state' (e.g., cookies, localStorage) or any side effects, relying entirely on the annotation.

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 sentence, which is appropriate for a simple tool. However, it is too brief and could benefit from a bit more detail without becoming verbose.

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 (one parameter, read-only, output schema exists), the minimal description is partially adequate, but it fails to explain the 'session_id' parameter or the nature of the returned storage state. The output schema existence doesn't compensate for missing input semantics.

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 single parameter 'session_id' is required but the description does not explain its purpose or format. Schema description coverage is 0%, so the description adds no value beyond the schema's property name.

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 'Return browser storage state,' clearly specifying the verb (Return) and resource (browser storage state). It distinguishes itself from sibling 'browser_save_storage_state' which saves the state, making the purpose unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives, such as when to retrieve vs. save storage state. The description lacks any when-to-use or when-not-to-use context.

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