save_storage_state

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

With no annotations available, the description carries the full burden of behavioral disclosure. It warns that the file holds live authentication secrets and should be stored securely, which is a crucial behavioral trait. It also implies a write operation and gives restore instructions, though it does not mention overwriting behavior or failure modes.

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 compact and well-structured. It opens with a one-sentence purpose, adds a security note, gives restore context, and then lists arguments with clear explanations. Every sentence earns its place 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?

For a tool with only two parameters and an output schema, the description covers all essential aspects: what is saved, the security implications, how to restore, and parameter details. It is complete enough for an agent to invoke correctly without further assumptions.

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 must compensate. It explains that session_id is an existing session ID and suggests creating one via browse/extract, and that path is the file to write to. These explanations add significant meaning beyond the bare schema property names.

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 clearly states the tool's function: 'Save a session's cookies + localStorage (auth state) to a JSON file.' This is a specific verb-plus-resource that distinguishes it from sibling tools like browse, extract, or close_session. The scope is well-defined: it saves session storage state, not just any data.

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 clear context: it explains that restoring is done via BROWSER_STORAGE_STATE and specifies that session_id must be an existing session (created via browse/extract). It does not explicitly name alternatives or when-not-to-use, but the context is sufficient for most agents.

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