browser_close

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description reveals a non-obvious behavioral trait: only a server-launched browser is actually stopped, while attach-mode browsers are left running. This is valuable context; it could go further by stating what happens to the session after the tab closes, but the key caveat is present.

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 tight and front-loaded: one clear action, one conditional flag, and one caveat. Every sentence earns its place, with no redundant filler.

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?

Given its moderate complexity, an output schema, and annotations, the description covers the main behaviors an agent needs: what is closed, when the browser stops, and how attach mode differs. The main gap is the undocumented session parameter, which keeps this from a 5.

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?

With 0% schema description coverage, the description must carry parameter meaning. It clearly explains shutdown_browser=True and its attach-mode limits, but it leaves the session parameter undefined beyond the schema title 'Session', so an agent must infer what a session is and what values are valid.

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 opening sentence names a specific verb and resource: it closes a session's tab, with an optional flag to stop the browser. This is clear and not a restatement of the tool name, but it does not explicitly differentiate the tool from siblings such as browser_tabs or browser_act.

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 conditional guidance for shutdown_browser and explains attach-mode behavior, but it never states when to prefer browser_close over browser_tabs, browser_act, or other siblings. The intended use is implied rather than explicitly contrasted.

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