Detach from a page

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

With no annotations, the description carries the full behavioral burden. It adds valuable non-obvious context that buffered events are discarded, but it does not disclose permissions, reversibility, whether the page is closed, or the effect on other attached clients.

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?

One tight sentence with zero waste. The core action and its most important side effect are front-loaded.

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 one-parameter tool with no output schema, this covers the basic action and one key side effect. It remains incomplete about whether detaching closes the page, whether it can be reattached, and what a caller should expect afterward.

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 description coverage is 100%, and the single optional `target_id` is fully documented in the schema. The description adds no parameter-specific meaning beyond that baseline, which is appropriate here.

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: "Disconnect from a page." This is clearly the counterpart to the sibling `attach`, though it does not explicitly name that sibling or distinguish itself from `list_targets`/`get_console`.

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 implied: call this when you want to disconnect from a page, and the note about discarding buffered events hints at a consequence. However, there is no explicit when-to-use vs. when-not guidance, no mention of `attach`, and no prerequisites.

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