browser_close

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

The description only repeats the core action and does not add meaningful behavioral context beyond what the annotations already signal (destructiveHint=true, readOnlyHint=false). It does not explain whether the current tab, all tabs, or the whole browser is closed, nor whether unsaved state is affected. There is no contradiction with the annotations.

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 extremely short and front-loaded with the only essential content. However, the underspecification of 'page' versus 'browser' makes it slightly less effective than a crisp one-sentence definition could be.

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 operation, 'Close the page' is minimally viable, especially with annotations already marking it as destructive. Still, the scope ambiguity (tab vs. browser) and absence of any note about side effects leave room for an agent to mispredict the tool's impact.

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 and the schema coverage is trivially 100%. A baseline of 4 applies because there is no parameter semantics for the description to clarify.

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 uses a specific verb and resource: 'Close the page.' It is clear enough to distinguish from navigation or resizing siblings, though 'page' is slightly ambiguous (current tab vs. entire browser) and the annotation title says 'Close browser.'

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 tool versus alternatives like browser_navigate, browser_tabs, or browser_navigate_back. The description gives no context about prerequisites, expected state, or when not to call it.

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