browser_connect

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

With no annotations, the description carries full responsibility for disclosing behavior. It only states the purpose ('for debugging') but does not explain what 'connect' entails, whether it changes browser state, requires a previously launched debugging server, or returns any confirmation. No side effects or prerequisites are disclosed.

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 a single sentence, concise and front-loaded with the action. Every word contributes to the core purpose, and there is no redundant or tangential information.

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?

The tool is part of a debugging workflow with siblings like browser_list_tabs and browser_disconnect, but the description does not explain how tabId is obtained, what happens after connection, or how to interpret the lack of an output schema. Given the complexity of the workflow, the description is too sparse to be fully actionable.

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%, with all three parameters (host, port, tabId) having descriptions. The tool description adds no parameter-level semantics beyond what the schema provides, so the baseline score of 3 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: 'Connect to a specific browser tab for debugging.' It uses a specific verb ('Connect') and resource ('specific browser tab'), and the 'for debugging' qualifier positions it within the tool suite. It distinguishes itself from siblings like browser_list_tabs (listing) and browser_disconnect (disconnecting).

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?

No explicit guidance is provided about when to use this tool versus alternatives, nor any prerequisites such as launching the browser with a debugging port. The description only implies usage for debugging, but lacks direction to first list tabs via browser_list_tabs or to prefer other tools in specific scenarios.

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