browser_close

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

No annotations are provided, so the description carries the burden. It discloses the main side effect (clears the browser session), which is helpful. However, it does not mention destructive nature (closing all open tabs) or whether the action is reversible, but for a close operation the intent is clear.

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?

A single sentence with no filler. The primary action ('closes the controlled browser') is front-loaded, and the parenthetical adds a key side effect without bloating the description.

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 parameterless tool with low complexity, the description is adequate. It explains the core behavior and session-clearing effect. Though it doesn't mention return values or error conditions, these are unlikely to be critical for a close operation, and no output schema exists to demand more.

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?

Tool has zero parameters, so schema coverage is trivially 100% and there is nothing to document. Baseline for 0 params is 4, and the description does not need to add parameter detail.

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?

Description clearly states a specific verb and resource: 'Closes the controlled browser.' It adds '(clears the browser session)' which distinguishes its effect from simply closing a tab, though it does not explicitly name sibling tools like tab_close. Still, the action is unambiguous and unique among the browser_* family.

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?

No guidance on when to use this tool versus alternatives such as tab_close or session_delete. The description only states what it does without explaining when to choose it over other close/cleanup operations.

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