browser_save_session

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the disk snapshot, per-origin localStorage condition, and temp-tab side effect, but omits overwrite behavior, error cases, permissions/security details, and what is returned.

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?

Front-loads the purpose, then gives a use case, then documents the arguments. Every sentence earns its place and the structure makes the most important details easy to find.

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?

With no annotations or output schema, the description covers purpose, usage, both parameters, and key side effects well enough to invoke the tool. Missing return semantics and overwrite behavior are minor gaps but leave the definition slightly incomplete.

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 fully, which it does. It explains that name becomes a filename under ~/claude-zen-sessions/ and that urls are origins whose cookies and localStorage are snapshotted, each opened briefly in a temp tab.

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?

States a specific verb (snapshot/save) and resources (cookies, per-origin localStorage) to disk. The name and use case distinguish it from browser_cookies and browser_load_session.

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?

Provides an explicit use case: log in interactively once, save the session, then let parallel agents load it for authenticated work. It names the loading alternative conceptually but does not explicitly route to browser_load_session or state when not to use it.

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