close_browser

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

With no annotations, the description carries the behavioral transparency burden; 'end the session' conveys finality and is a useful disclosure. However, it does not mention side effects such as loss of browser state, closing all tabs, or that a new browser must be started before further actions.

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 a single short sentence that leads with the action and includes no filler or redundant details. It is easy for an agent to parse quickly.

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, parameterless, terminal action this description is largely complete, and the presence of an output schema means return values do not need to be described. It lacks only explicit usage context and side-effect caveats, which keeps it from a 5.

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 the input schema is empty, so there is no parameter information for the description to add. The baseline for a zero-parameter tool applies here.

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 and resource ('Close the browser') and adds that the session is ended, making the operation unambiguous. In a sibling list that includes close_active_tab, this wording clearly identifies a browser-level shutdown rather than a tab-level action.

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 states only what the tool does, not when to call it or how it relates to alternatives such as close_active_tab. There is no mention of end-of-session workflow, prerequisites, or situations where this tool should be avoided.

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