playwright__browser_close

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

The description says 'Close the page' while annotations (title: 'Close browser', destructiveHint: true, readOnlyHint: false) indicate it closes the browser. This contradiction between description and annotations makes the behavioral intent unclear. The description also fails to detail what state changes occur, confirmation steps, or whether the entire session is terminated.

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 (single sentence) but underspecified. While brevity is valued, the content is too sparse to be effectively informative, especially given the contradiction with annotations.

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 the tool is simple with no parameters and no output schema, the description should at least unambiguously state what is closed (browser vs page) and any notable side effects. It fails to do so, leaving the agent confused about the tool's exact scope.

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?

There are no parameters (schema coverage 100% with empty object), so the description does not need to add parameter information. The baseline for zero parameters is 4, and the description does not detract from this.

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 'Close the page', which is a verb+resource, but the tool name and annotation title indicate it closes the browser. This mismatch creates ambiguity about the actual resource being closed, lowering clarity. It does distinguish from siblings since no other sibling closes anything, but the inconsistency hurts the score.

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 on when to use this tool versus alternatives such as navigating away or using a different browser management tool. There is no context on prerequisites, side effects, or situations to avoid, leaving the agent to infer usage solely from the tool name.

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