browser_close

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It usefully explains that cookies persist in a specified profile path and that a fresh-profile launch removes the temporary profile. This goes beyond the bare verb 'close' and gives the agent crucial context about state persistence and destructive side effects.

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 concise sentences deliver the core action first, then the persistence caveats. No unnecessary filler. Every sentence contributes meaningful 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?

Given the tool's simplicity, zero parameters, and absence of an output schema, the description covers all essential aspects: what it closes, what is preserved, and what is removed under fresh-profile mode. An agent has enough information to invoke and anticipate side effects 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?

The tool has zero parameters, so there is no parameter information for the description to add beyond the schema. With 0 params, the baseline of 4 applies. The description appropriately focuses on behavioral effects instead of parameter details.

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 opens with a specific verb and resource: 'Close the browser.' This clearly distinguishes it from sibling tools like tab_close (which closes only a tab), browser_launch (which starts the browser), and browser_recover (which attempts recovery). The scope is unambiguous.

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 intended use is implied: call this when you want to end the browser session. However, it provides no explicit guidance about when this should be preferred over alternatives like reset_profile or browser_recover, nor any 'when not to use' statement. The context is clear but the routing guidance is absent.

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