browser_session

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

No annotations are provided, so the description carries the full burden. It mentions that each 'create' session has independent context/cookie/storage and that extensionPath forces headless=false. However, it does not disclose destructive effects (close deletes session), error handling, or required permissions.

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 succinct paragraph that covers purpose, modes, and key parameter interactions. However, it could be better structured (e.g., bullet points for modes) for easier scanning.

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 description explains the modes adequately but does not describe the return value for the 'list' mode or any error scenarios. With 8 parameters and no output schema, more detail on expected outputs and errors would improve completeness.

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 coverage is 100%, so the description adds limited value. It does clarify the relationship between sessionName/name and extensionPath/loadExtensionPath, and notes that extensionPath forces headless=false. This justifies a score above baseline 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 clearly states it's a browser session management tool, enumerates four sub-modes (list, create, switch, close), and mentions it merges previously separate tools. It distinguishes itself from siblings by being the consolidated session manager.

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 explains when to use each mode via the mode parameter and mentions that this tool supersedes browser_session_create, browser_session_switch, browser_session_close, and browser_sessions. However, it doesn't explicitly state when not to use this tool in favor of other browser tools.

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