playwright__browser_close

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

The description directly contradicts the annotations: it says 'Close the page' while the annotation title says 'Close browser' and the tool name is browser_close. Because of this contradiction, per rubric the behavioral transparency score is 1.

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 and front-loaded, with no filler words. However, the single phrase is underspecified and the page/browser inconsistency prevents it from being a model of effective conciseness.

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 action, the description omits side effects like losing unsaved state or closing all tabs, despite annotations carrying the destructive hint. The ambiguity between page and browser also leaves the tool's actual scope unclear, making the definition incomplete for correct use.

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 schema description coverage is 100%, so the schema fully documents the input. With no parameters to explain, the description need not add anything, and the baseline of 4 applies.

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 a verb and resource ('Close the page'), so it is not a tautology, but it conflicts with the tool name (playwright__browser_close) and the annotation title ('Close browser'). This page-vs-browser mismatch leaves the actual target ambiguous and potentially misleading.

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 about when to use this tool versus any of the many sibling browser tools. It does not mention alternatives, prerequisites, or context (e.g., whether it should be used before navigating away or when done with a session).

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