browser_close

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

With no annotations provided, the description carries full burden of behavioral disclosure. It implies a destructive action (closing sessions) but does not mention irreversibility, impact on the current session, or whether closing all sessions has any side effects like terminating the browser. This is a significant gap for a destructive operation.

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 a single, concise sentence with no wasted words. It is front-loaded with the core action, but the brevity sacrifices necessary detail. It earns points for being succinct, though it under-specifies.

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?

The tool has two parameters, no annotations, and no output schema. The description does not clarify the relationship between sessionId and all, what happens after closing, or any expected return values. For a destructive operation with minimal structured context, the description is insufficiently complete.

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?

Schema description coverage is 0%, so the description must compensate. It mentions 'all=true' but does not explain the sessionId parameter, whether it is required, or how it interacts with all. The description adds minimal meaning beyond the schema, leaving parameter usage ambiguous.

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 states a clear verb ('close') and resource ('session'), and specifies the scope with 'all=true' to close all sessions. It is specific enough to distinguish from sibling tools like browser_close_tab, which targets tabs rather than sessions.

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. It only explains the all flag but does not mention when closing sessions is appropriate, prerequisites, or exclusions. The description is purely functional with no context about typical use cases.

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