Close the browser and wipe all session state—tabs, references, and console logs—to start fresh. For CDP connections, detach without terminating the browser.
Shut down the browser and forget all state (tabs, refs, console log).
In CDP mode this detaches from the attached browser without closing it.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description fully discloses the behavioral consequences: it forgets all state (tabs, refs, console log) and behaves differently in CDP mode. This adds significant value beyond the minimal 'close browser' and warns agents of state loss and mode-specific behavior.
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?
Two sentences with zero filler. The main action is front-loaded, and the CDP-mode exception is a separate, necessary sentence. Every word contributes to the agent's understanding.
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?
For a zero-parameter tool with an output schema, the description fully covers what an agent needs to know: the shutdown action, the state loss details, and the CDP-mode deviation. Nothing crucial is missing.
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 zero parameters and 100% coverage, so there are no parameter semantics to explain. Per the baseline for tools with no parameters, a score of 4 is appropriate; the description appropriately focuses on behavior instead.
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 ('shut down') and resource ('browser') and explicitly states the scope ('forget all state (tabs, refs, console log)'). It distinguishes itself from siblings like browser_tab_close by indicating this closes the entire browser rather than a single tab, and from navigation tools by the shutdown action.
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 gives clear context about when this tool is relevant—ending a browser session—and provides the CDP-mode caveat that it detaches instead of closes. It does not explicitly name alternatives or state when not to use it, but the purpose is unambiguous enough for an agent to infer appropriate usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.