browser_save_storage_state

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

With no annotations provided, the description must fully disclose behavioral traits. It states the save action but does not explain whether the file is overwritten or appended, what format is used (e.g., JSON), or whether it requires specific permissions. Missing critical behavioral context for a mutation tool.

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 concise at one sentence, which is efficient but lacks necessary detail. It could be improved by adding a brief explanation of parameters or usage context. The structure is front-loaded but insufficient.

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 no annotations, low schema coverage, and the presence of an output schema, the description should explain return values or side effects. It does not mention what the tool returns (e.g., the saved path) or any confirmation. The tool is incomplete for effective use.

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 description coverage is 0%, so the description should add meaning to the parameters. It does not explain that 'session_id' identifies a browser session or that 'path' is the file destination. The description adds no value beyond the parameter names themselves.

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 'Save browser storage state to a file' clearly states the action (save) and resource (browser storage state to a file). It distinguishes from sibling tools like browser_get_storage_state which presumably retrieves state rather than saving to a file. However, it does not specify what 'storage state' includes (e.g., cookies, local storage), which could be ambiguous.

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. For instance, there is no mention of using browser_get_storage_state to retrieve state first or that this tool overwrites existing files. The description lacks context about prerequisites or exclusions.

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