browser_saveCookies

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

The description discloses that sessions persist across agent and server restarts, a key non-obvious behavioral trait. It also implies persistence via the phrase 'works for days,' but it doesn't address overwrite 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 only two sentences and front-loads the purpose. The quoted tagline and persistence statement are meaningful and concise, with no wasted words.

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, no output schema), the description covers the core action and persistence, which is sufficient. It could mention behavior for duplicate names, but that's a minor gap.

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 input schema already fully describes the 'name' parameter with examples, so the description adds no extra parameter semantics. Per the baseline rule for high schema coverage, this scores 3.

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 a specific verb ('Save') and resource ('current browser session (cookies)'), clearly distinguishing it from sibling tools like browser_loadCookies or browser_listSessions.

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 tagline 'Login once, agent works for days' implies the primary use case is saving an authenticated session after login, giving clear contextual guidance. It does not explicitly mention alternatives or when not to use, but the context is strong enough.

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