browser_close

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

No annotations are provided, so the description bears full responsibility. It discloses that the session is closed, resources released, and active screencast/recording stopped. This covers key behavioral traits, though it could mention if the action is irreversible or if there are confirmations.

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?

Two sentences, front-loaded with the core action, no redundant information. Every word contributes value.

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 simple tool with no parameters and no output schema, the description is sufficient. It covers the primary action and additional effects (stops screencast/recording). Minor gap: doesn't mention if it also closes all tabs or if it's part of a lifecycle (e.g., must be preceded by browser_launch).

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 (0 params, 100% schema coverage). Per guidelines, baseline is 4. The description doesn't need to add parameter meaning.

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 clearly states the verb ('Close'), the resource ('active browser session'), and the action ('release all resources'). It distinguishes from siblings like browser_close_tab, browser_launch, and browser_stop_recording by specifying it affects the entire session and stops screencast/recording.

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 implies when to use (end session), but lacks explicit when-not-to-use or alternative tools. For example, it doesn't mention that browser_close_tab is for individual tabs or that browser_stop_recording stops recording without closing.

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