browser_connect

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

With no annotations provided, the description carries the full burden of disclosing side effects, prerequisites, or error behavior. It only says 'connect' without explaining whether it is a read-only operation, what happens if the endpoint is unreachable, or whether it modifies browser state.

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 concise sentence with no unnecessary words. It is immediately clear and front-loaded, though brief.

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 no annotations, no output schema, and no parameter descriptions, the one-sentence description is insufficient. It does not cover return values, parameter usage, or when to use this tool relative to siblings, leaving significant gaps for the agent.

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 0%, and the description does not mention or explain the two parameters (endpointUrl, debuggingPort). It provides no guidance on how to specify the endpoint, leaving the agent to guess from the schema alone.

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 ('connect') and resource ('existing Chromium remote-debugging endpoint'), and the word 'existing' distinguishes it from browser_launch, which presumably starts a new browser.

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 'existing endpoint' gives clear context that this tool is for attaching to an already-running browser, implying it is not for launching a new one. However, it does not explicitly mention alternatives like browser_launch, so it stops short of full exclusion guidance.

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