browser_use_tunnel

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states 'launch' and 'through VPN tunnel' with no details about slot auto-assignment, tunnel selection, readiness, errors, or side effects. The agent is left uncertain about what happens after invoking the tool.

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, front-loaded sentence with no wasted words. It states the core action and the network path efficiently, making it easy to scan and understand.

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 moderate complexity (2 optional parameters, output schema present), the description is too sparse. It does not explain what a 'browser slot' is, how the returned output relates to the launched browser, or any prerequisites such as tunnel availability. The minimal guidance leaves gaps for safe and effective use.

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?

The input schema provides complete descriptions for both parameters (slot and tunnel_id), achieving 100% schema coverage. The description adds no additional parameter meaning beyond what the schema already offers, so the baseline 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 uses a specific verb ('Launch') and resource ('a browser slot') with a clear method ('through a Shade VPN tunnel'). It distinguishes this tool from siblings like browser_use_tor and browser_use_residential by specifying the tunnel-based network path.

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 browser slot over a VPN tunnel is needed, which is a distinct scenario from Tor or residential proxies. However, it provides no explicit when-to-use or when-not-to-use guidance, nor mentions alternatives. The context is inferred rather than stated.

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