cdp_detachDetach NAVIG from the current browser debugging session while keeping the browser open and CDP port active. Use it to release control of tabs without closing the browser.
Disconnect NAVIG's session but LEAVE the browser open (port stays on).
| Name | Required | Description | Default |
|---|---|---|---|
| all | No | Detach from every attached tab, not just the current one | |
| port | No | CDP debug port (default 9222). |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already flag destructiveHint=true and readOnlyHint=false. The description usefully adds the post-condition that the browser and port remain alive, but it does not disclose whether tabs/session state is recoverable, whether re-attachment is possible, or what an agent should expect afterward.
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 tight sentence with the critical distinction (session gone, browser alive) front-loaded via capitalization for emphasis. No waste, though it is terse enough to leave some behavior unstated.
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 two-parameter detach tool with full schema coverage and annotations declaring the mutation profile, the description covers the essential behavior an agent needs. Lacking an output schema, it could say more about the resulting state, but the core is covered.
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?
Schema coverage is 100%, so both 'all' and 'port' are already documented in the schema. The description's '(port stays on)' gestures at the port parameter's role but adds no syntax or behavioral detail beyond it. Baseline 3 applies when the schema carries the parameters.
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 (NAVIG's session), plus the key scope qualifier that the browser stays open. It distinguishes the effect from a full stop, though it never names the sibling cdp_stop it implicitly contrasts with.
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 phrase 'but LEAVE the browser open' implies the use case (disconnect without tearing down the browser), but there is no explicit when-to-use or when-not-to-use guidance against cdp_stop, cdp_launch, or cdp_launched. Usage is inferable rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.