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

Annotations already declare destructiveHint=true and readOnlyHint=false, so safety is covered by structured data. The description adds no behavioral context beyond the name — it doesn't say whether the close is graceful, whether tabs/session state is lost, or what happens to an unknown address. With annotations carrying the burden a 2 is still warranted because the description contributes essentially nothing new.

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 front-loaded sentence with zero filler, though its brevity edges into under-specification rather than disciplined concision.

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 destructive tool with no output schema and a near-identical sibling, the description omits the consequences of closing and the disconnect-vs-close distinction an agent needs to choose correctly.

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 coverage is 100% and the single `address` parameter is fully documented in the schema, so the description need not repeat it. Baseline 3 applies since the description adds no format or sourcing detail (e.g., where to obtain the address) beyond the schema.

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?

States a specific verb and resource ("Close a specific browser"), which tells an agent what the tool does. However, a sibling `disconnect_browser` exists and the description offers nothing to distinguish closing from disconnecting, so differentiation from siblings is absent.

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?

There is no guidance on when to use this versus `disconnect_browser` or `browser_workspace`, nor any prerequisite such as needing an active connection first. The agent must infer everything from the name alone.

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