close_browser

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

With no annotations, the description fully discloses side effects: in CDP mode it closes the tab and disconnects but leaves Chrome running; in standard mode it saves the session (if named) and closes the browser. This is transparent and goes beyond the tool name.

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 concise and well-structured, presenting the core action first, then breaking down behavior by mode. Every sentence provides valuable information without redundancy.

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, the description is complete: it explains the outcome in both operating modes, addresses session persistence, and clarifies that only the agent's tab is closed. The existence of an output schema means the return value does not need to be described.

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 are no semantics to explain. The description provides necessary mode-related context that the schema (empty) cannot convey. Baseline of 4 is appropriate for a parameterless tool.

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 tool's function: 'Close the tab and disconnect from the browser.' It distinguishes between CDP and standard modes, making the scope explicit (closes only the tab the agent opened) and differentiating it from siblings like open_browser and navigate.

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 explains behavioral context by describing what happens in each mode (CDP vs standard), which implicitly tells the user when this tool is appropriate. It does not explicitly mention alternatives, but for a cleanup/teardown tool the usage is clear from the name and context.

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