manage_browser_session

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

With no annotations, the description bears full responsibility for disclosing behavior. It notes the scope (cookies + storage) but does not reveal important traits such as the destructive nature of 'clear', the overwriting behavior of 'load', or any side effects like logging out. The schema provides some hints (e.g., 'clear (logout)'), but the description itself is minimal and lacks these disclosures.

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 a single, tightly-written sentence that lists all four operations and the resource scope. Every word contributes to the core meaning, with no filler or repetition. This is exemplary conciseness for a multi-function tool.

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?

The tool has moderate complexity (6 params, 4 operations) and no output schema, but the schema descriptions are detailed. Yet the description misses return values (e.g., what export returns, result of save/load/clear) and important caveats like loading overwriting the current session. It is adequate for a high-level overview but leaves gaps that require the agent to infer from operation names.

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 has 100% description coverage for all six parameters, so the description adds no additional meaning. The description aligns with the parameter concepts (cookies/storage) but does not enrich beyond what the schema already explains. Baseline 3 is appropriate.

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 with specific verbs (save, load, clear, export) and resource (browser session: cookies + storage). It is distinct in that it performs multiple operations in one call, but it doesn't explicitly differentiate from sibling tools that handle individual operations (e.g., clear_cookies, export_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?

The phrase 'in one call' implies a combined usage scenario, suggesting users should use this when they want to handle multiple session operations together. However, it does not explicitly state when to prefer this over individual cookie/storage tools or mention any exclusions, leaving the guidance implied rather than explicit.

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