disconnect

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

With no annotations, the description carries the full behavioral burden. It usefully discloses one key side-effect constraint (the app stays alive), which is the most important thing to know. However, it says nothing about whether the CDP session can be resumed, whether the operation is idempotent, or what state is torn down.

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 short sentence with the core action front-loaded and the most decision-relevant caveat (does not close the app) placed immediately after. Nothing to trim.

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, annotation-free teardown tool with no output schema, the description covers the essential behavior. It would be complete at 5 if it noted the session/connection state left behind or whether the agent must reconnect before further CDP calls.

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 takes zero parameters, so there is nothing to document; baseline 4 applies. The empty schema is consistent with the description, which implies no arguments are required.

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 (disconnect) and resource (CDP), and the parenthetical distinguishes it from the sibling 'close' by clarifying that the app itself is not terminated. An agent can route between close and disconnect without opening either schema.

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 through the contrast with 'close' — the agent can infer this is the right call when it wants to detach from the browser/session while leaving the app running. There is no explicit statement of when to call it, in what order relative to connect/launch, or whether reconnection is possible.

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