browser_close

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

With no annotations provided, the description carries the full behavioral disclosure burden. It meaningfully explains the side effects: releasing resources, disconnecting external CDP browsers, and actually closing managed Chrome/Playwright browsers. This is strong behavioral transparency, though it could additionally mention idempotence or error behavior.

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 two short sentences with no filler. The primary action is front-loaded, and the important behavioral nuance about CDP versus managed browsers is delivered efficiently.

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 close-operation tool with an output schema present, the description is complete: it states the core action, the resource affected, and the key behavioral difference between connection types. Nothing essential for the agent to call the tool correctly is missing.

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 coverage is 100%, so there is no parameter burden on the description. The baseline of 4 applies because the description accurately reflects a parameterless operation without needing to add parameter-level detail.

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 ('关闭' / close) and a clear resource ('Playwright 浏览器'), and further distinguishes behaviors for CDP-connected external browsers versus managed browsers. This clearly separates the tool from siblings like browser_open, browser_start, and browser_connect.

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?

The description clearly implies when to use the tool (when a browser or CDP connection should be closed) and provides context about how different connection types are handled. However, it does not explicitly state alternatives, exclusions, or when not to use this tool, leaving the usage guidance mostly inferred.

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