Close browser

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

With destructiveHint=true already signaling destructive behavior, the description adds no additional context about what actually gets closed—whether it closes all pages, terminates the browser session, or has irreversible effects. The page vs. browser ambiguity further obscures behavioral impact.

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 short sentence, making it highly concise and front-loaded. However, its brevity contributes to ambiguity, so while structurally concise, it sacrifices clarity.

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's scope (browser vs. page) is unresolved, and there is no mention of what happens to open tabs, whether the action is reversible, or what the expected outcome is. Given the tool's simplicity, a clearer statement about closing the entire browser instance would make it 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?

The only parameter is an optional _meta object with no functional significance, so the schema already covers the parameter surface. The description adds nothing about parameters, but that is acceptable since there are no meaningful parameters to explain.

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 'Close the page' conflicts with the tool name 'browser_close' and title 'Close browser', creating ambiguity about whether it closes the entire browser or just the current page/tab. This is misleading for agents that know the distinction between a page and a browser in automation contexts.

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 usage guidance is provided. The description does not mention when to use this tool versus alternatives like browser_navigate_back or browser_tabs, nor any prerequisites or side effects. Agents are left to infer the appropriate context.

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