Connect to a browser over CDP

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

The description discloses that the tool attaches to an existing Chrome instance and that it can switch browsers/tabs. It does not contradict the annotations (readOnlyHint=false, destructiveHint=false) and adds useful behavioral context without overstating side effects.

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 two short sentences with no redundant or filler content. It is direct, readable, and front-loads the core action before the use case.

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?

Given the low complexity (all optional parameters, no output schema), the description is sufficiently complete. It explains both the mechanism and the intent, though it relies on the schema for parameter details.

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 schema already provides full descriptions for all six parameters, so baseline is appropriate. The description itself does not add extra parameter semantics, but none are needed because the schema coverage is complete.

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 action ('Attach Blinkwire to a Chrome instance exposing the DevTools Protocol') and the practical purpose ('switch browsers or tabs without restarting the server'). It is unambiguous about what the tool does at a high level.

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 description explicitly says when to use this tool: to switch browsers or tabs without restarting the server. It does not deeply contrast with sibling tools, but the stated use case is enough to guide selection in most situations.

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