Close Browser

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

The description discloses concrete behavioral effects: the session is closed, persistent browser state ends, and resources are released. It lists specific affected state such as open tabs, cookies, navigation history, and page state. It explicitly confirms idempotent behavior, consistent with the idempotentHint annotation, without contradicting any annotation.

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 compact and front-loaded: it states the core action in the first sentence, then gives usage context and safety confirmation. Every sentence contributes meaningful information without redundancy or 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?

For a zero-parameter tool with existing output schema, the description is fully sufficient. It covers the operation, the reason to call it, the consequence of closing, the alternative for subsequent sessions, and the no-op safety case. Nothing needed for correct invocation is missing.

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 semantic ambiguity to resolve. Per the baseline guidance for no-parameter tools, a score of 4 is appropriate even though the description adds no parameter-specific 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 clearly states the specific verb and resource: 'Close the active browser session and release browser resources.' This immediately differentiates it from sibling tools like start_browser, open_url, and manage_tabs. 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 description explicitly says when to call it: 'Call this when the browser automation workflow is finished.' It also names the alternative for future work: 'If browser automation is needed afterward, start a new session with start_browser.' It even covers the edge case of calling with no active session.

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