Close the browser session

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

Explains side effects beyond annotations: stops the worker, closes the Chrome window (or only disconnects in cdp), and confirms queued tasks persist. The description gives concrete behavioral context that annotations (readOnlyHint=false, destructiveHint=false) do not fully convey.

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, information-dense, with the primary action front-loaded and the cdp caveat and persistence detail following. No filler or redundant phrasing.

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 no-parameter tool with no output schema, the description fully covers what it does, its side effects, and follow-up behavior (queue persistence and relaunch). Nothing essential 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 tool has zero parameters, so schema coverage is trivially 100% with an empty object. The description doesn't need to explain parameters; the baseline of 4 applies. It correctly adds no param-related noise.

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 action: 'Stops the background worker and closes the Chrome window this server launched', with a specific resource (browser session) and a distinction for cdp mode. This differentiates it from siblings like browser_status or debug_navigate.

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 context on behavior in cdp mode and notes that queued tasks remain, implying it's safe to close. It mentions queue_start as the relaunch mechanism, but doesn't explicitly list when not to use this tool or compare with siblings. Still clear enough for an agent to decide.

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