browser_open

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

No annotations provided, but the description discloses behavioral traits: stealthy operation, prerequisites for cdp mode, and that it connects or opens a browser. It could mention effects like reconnecting if already open.

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 well-structured with line breaks and bullet points, though slightly verbose. Every sentence adds value, but it could be more concise.

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 complexity (two modes, 6 parameters) and no output schema, the description covers most modes and parameters but omits headless and does not specify return value or prerequisites beyond cdp mode. Suggests using capture, which helps.

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 has 0% parameter description coverage, but the description explains url, mode, cdp_url, channel, and user_data_dir in context, adding meaning beyond the schema. The headless parameter is not mentioned.

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 'Open/connect a browser for stealthy work' and distinguishes two modes (cdp and stealth), making it specific and differentiating from siblings like browser_close and browser_goto.

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 explains when to use each mode (cdp for maximum stealth and live sessions, stealth for own browser with persistent profile) and suggests using capture after opening, but does not explicitly state when not to use the tool.

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