browser_stop

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

No annotations are provided, so the description carries the full behavioral burden, and it is thin. The word 'Close' implies a destructive terminal action, but the description does not say whether it destroys the session/tabs, whether it is idempotent when nothing is open, or whether it errors. Only the scope hint ('single agent browser') adds context.

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?

A single compact sentence with the action front-loaded and the parameter caveat trailing. Nothing is wasted, though the extreme brevity leaves gaps that a slightly longer description could close.

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?

The output schema covers return values, so those need not be explained. Still, for a tool with no annotations and 0% parameter coverage, the definition is minimal: it omits the state-destroying effects of closing the browser and the behavior when no session exists.

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?

With 1 parameter and 0% schema description coverage, the description is the only source of parameter meaning, and it does supply the key fact: 'session_id is usually omitted,' signalling the parameter is optional and normally defaulted. It never explains what a non-empty session_id does or what values are valid.

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?

States a specific verb and resource: 'Close the single agent browser.' The word 'single' clarifies scope, and close is clearly the inverse of the sibling browser_start. It does not explicitly name siblings, but the operation is unambiguous.

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?

Usage is only implied: you call it when you want to shut the browser down. There is no statement of when not to call it, what happens if no browser is running, or how it relates to alternatives such as calling browser_start again.

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