browser_open

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

With no annotations, the description carries full behavioral burden and succeeds: it discloses that each session is an independent Chrome instance, that multiple sessions can run simultaneously, that nodriver bypasses bot detection, and that traffic can be routed through a proxy port. This goes well beyond the schema.

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 a bold opening sentence, a numbered startup sequence, and an Args section. Every sentence provides actionable information—no filler or redundancy—making it appropriately sized and easy to scan.

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's complexity (session management, proxy dependency, headless mode), the description covers all essential aspects: prerequisites, sequencing, multi-session use, anti-bot behavior, and parameter effects. The presence of an output schema means return-value details are not the description's job.

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?

Although schema description coverage is 0%, the description thoroughly explains each parameter: session_name for unique names, proxy_port must match manage_proxy and 0 disables routing, headless default true and false for visual debugging. This adds critical meaning the schema lacks.

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 uses a specific verb ('Launch') and clearly identifies the resource ('a new Chrome browser session with anti-bot bypass'). It distinguishes this tool from siblings by explicitly stating it must be called before any other browser_* tool and explaining its session-launching role.

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?

Provides explicit usage context: 'Call this BEFORE any other browser_* tool' and a numbered startup sequence with manage_proxy and browser_go. It also explains when multiple sessions are useful for multi-user testing, giving the agent clear guidance on when to invoke this tool.

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