Browser Session Save Auth

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

With no annotations, the description carries the behavioral burden. It discloses that cookies and localStorage are persisted and that the profile survives restarts, which is valuable. However, it does not disclose whether an existing profile is overwritten, merged, or rejected, nor any side effects on the current session.

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 two tight sentences with the core action front-loaded and the restore workflow stated immediately after. Every sentence adds useful information and there is no filler.

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?

Although the output schema exists and the core purpose is clear, the description is not complete enough because one of two required parameters ('name') has no semantic guidance. It also omits overwrite/duplicate behavior, which matters for a persistence operation on named profiles.

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 explain both required parameters. It clarifies profile_name through the restore example, but the 'name' parameter is completely unexplained and not even mentioned in the description, leaving a critical ambiguity.

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 ('Persist') and resource ('cookies + localStorage') and clearly states the output is a named profile. It also names the restore counterpart, browser_session_new, which distinguishes it from sibling session management tools.

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?

It gives clear usage context: save the session for later restores, especially 'for staying logged in across engagements.' It mentions the restore mechanism via browser_session_new, but does not explicitly state when not to use this tool or call out alternative save/load approaches.

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