disconnect

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Close the browser' implies a destructive/terminating action, but it doesn't state whether unsaved state is lost, whether it affects other sessions, or whether it is idempotent. The description is minimal and leaves these behavioral traits undisclosed.

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 with no wasted words. It is appropriately sized for a simple tool, though it could add a brief note about side effects without becoming verbose.

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 tool that terminates a browser session, the description is incomplete. It doesn't mention side effects, whether it is safe to call when no browser is open, or how it relates to connect/open_url. The output schema exists but doesn't compensate for missing behavioral context.

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, so the schema provides no parameter semantics to add. The description correctly implies no arguments are needed. Baseline 4 is appropriate for a no-parameter tool.

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 'Close the browser.' is a clear verb+resource statement that distinguishes this from siblings like connect and open_url. However, it is terse and doesn't elaborate on scope (e.g., current browser session vs all browser contexts), which leaves some ambiguity for an agent deciding whether this is the right tool.

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?

No guidance is given on when to use this tool versus alternatives. The sibling list includes connect and open_url, which are related, but the description does not state conditions like 'use when done with the browser session' or 'not needed if the browser was opened by another tool.'

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