disconnect

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

With no annotations provided, the description must carry the behavioral disclosure. It clearly states it disconnects the session and clears in-memory pause state, which is beyond just the name. It doesn't mention side effects on breakpoints or reconnection, but for a simple disconnect operation, this is sufficient.

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 concise sentences that clearly state the action, the effect (clearing pause state), and the recommended usage context ('before connecting again'). No wasted words.

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 covers the action, side effects, and usage context. It's complete enough for an agent to decide when to use it, though it doesn't mention any potential errors or whether disconnect is idempotent.

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 secret, so parameter explanation is unnecessary. The description doesn't need to compensate for anything. Per the instructions, 0 params gives a baseline of 4, which is appropriate.

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 tool's function: 'Disconnect the current Chrome debugging session and clear in-memory pause state.' It uses a specific verb ('disconnect') and resource ('Chrome debugging session'), and distinguishes it from siblings like 'connect' and 'resume' by focusing on termination and clearing pause state.

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 instruction to 'use this to explicitly end a debug session before connecting again' gives clear context for when to use the tool. It implicitly contrasts with reconnecting, but doesn't explicitly name alternatives or exclusions, which is acceptable given the simplicity of the tool.

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