browser_close

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

Without annotations, the description carries the full burden and delivers crucial behavioral context: the page is destroyed, other browsers are unaffected, and identity is forgotten so reopening creates a new session. This covers side effects, scope, and a deliberate state-loss behavior that an agent could not infer otherwise.

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?

Efficiently organized: first sentence states the action, subsequent sentences explain the effects. No wasted words, though the identity-forgetting elaboration could be marginally tightened.

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?

A simple one-parameter tool with an output schema. The description thoroughly explains the behavioral impact, including subtle identity loss. However, it is incomplete regarding the parameter's meaning and default behavior, which an agent needs to call it correctly.

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 description coverage is 0%, and the description never mentions the 'browser' parameter, its enum values ('main', 'support'), or the default null behavior (which likely means closing the active browser). The parameter remains completely undocumented.

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 (close) and resource (browser), and clarifies the scope: it closes one browser, leaving the other sibling browser untouched. This distinguishes it from browser_open and other siblings, though it doesn't explicitly name which browser name is used.

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 implies this is for ending a browser session, but gives no explicit guidance on when to use this versus simply stopping interaction or leaving the browser open. No prerequisites or alternatives are mentioned.

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