browser_close

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

Annotations already indicate destructiveHint=true, so the destructive nature is clear. However, the description adds no behavioral context beyond that, such as what happens to unsaved data or whether the page can be reopened. With annotations present, the bar is lower, but the description still fails to add value.

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 concise at 4 words, with no wasted content. For a simple close action, this level of conciseness is optimal and well-structured.

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?

Given no parameters and no output schema, the description is barely adequate. It does not explain side effects, such as whether the browser closes the entire window or just the current tab, or how it interacts with multiple tabs. A minimal tool can get by with a short description, but it still lacks completeness.

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?

No parameters exist in the schema, and the description does not mention any. Since there are no parameters to explain, the description does not need to add semantic information. Baseline score of 4 is appropriate.

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' is a clear verb+resource combination. It is distinct from sibling tools like browser_navigate or browser_tabs, though very minimal. Could be more specific (e.g., current tab vs page).

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 is provided about when to use this tool versus alternatives like browser_navigate_back or browser_tabs. Agents have no context to decide which tool is appropriate for closing a tab vs page.

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