browser_close

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

The description adds 'release all resources,' which provides some behavioral context beyond the tool's name. However, with no annotations, it does not disclose potential side effects (e.g., losing unsaved state) or prerequisites (e.g., browser must be launched).

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, no filler. Every word earns its place: the action, what it releases, and when to call it.

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 no parameters and an existing output schema, the description adequately covers the tool's purpose and usage context. It could be enhanced by explicitly noting that it is for the stealth browser and mentioning potential outcomes (e.g., session ends).

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 no parameters and the schema coverage is 100%. The description does not need to add parameter details, so it meets the baseline for zero-parameter tools.

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: 'Close the stealth browser and release all resources.' It distinguishes from siblings like browser_close_page, which closes a single page instead of the entire browser.

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?

Includes the instruction 'Always call when done,' which implies it is a cleanup step called at the end of a session. However, it does not explicitly state when not to use it or mention alternative tools like browser_close_page for closing individual pages.

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