browser.connect_cdp

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only states 'connect', lacking details on authentication, error handling, side effects (e.g., does it open a new page?), return values, or prerequisites beyond remote debugging being enabled.

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 short sentence (12 words) with no wasted words, achieving conciseness. However, it sacrifices necessary detail, making it borderline under-specified for a connection tool.

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 tool complexity (CDP connection), no output schema, and no annotations, the description is insufficient. It omits return behavior (e.g., what is returned upon successful connection), prerequisites, and potential errors, leaving the agent underinformed.

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%, so the description must compensate. It fails to mention the two parameters 'endpoint' and 'slowMoMs' at all, providing no explanation of their meaning, format, or purpose. The agent is left guessing, especially for the non-obvious 'slowMoMs'.

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 verb 'connect' and the resource 'Chrome/Chromium with remote debugging enabled (CDP)'. It effectively distinguishes from sibling tools like 'browser.launch' and 'browser.launch_chrome_cdp', which create new browsers rather than connecting to existing ones.

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 implies usage when a remote debugging endpoint is available by mentioning 'existing Chrome/Chromium with remote debugging enabled'. However, it does not explicitly state when to use this tool over alternatives, nor does it provide exclusions or when-not-to-use guidance.

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