browser_close

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

Goes well beyond the annotations: it discloses that all tabs are closed, in-memory page state is discarded, the on-disk profile (cookies, logins) is preserved, attached endpoint browsers are also closed, and the next tool call auto-starts a fresh browser. This is exactly the kind of destructive-scope and lifecycle context annotations cannot 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?

Front-loaded with the core action and its consequences, then the alternative routing sentence. Slightly dense in the opening clause ('the browser agent-in-browser is driving') but every clause carries real information.

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 session-termination tool with no output schema, the description covers everything an agent needs: destruction scope, what survives, attached-browser behavior, and post-close lifecycle.

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?

Zero parameters, so there is nothing to document; baseline applies. The description does not need to explain inputs and correctly avoids doing so.

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?

States a specific verb (shut down) and resource (the browser the agent is driving), and explicitly contrasts with tab_close for closing a single page. An agent can distinguish it from tab_close, browser_status, and browsers_installed without opening a schema.

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?

Explicitly names the two situations to use it (finish a session, recover from a stuck browser) and the alternative for the narrower case (tab_close for one page). No inference required.

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