launch_browser

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

With no annotations, the description discloses that without the trio of parameters, the browser runs in a sandbox iframe causing Cloudflare to issue a hard challenge. This is critical behavioral information beyond what the schema reveals.

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 two paragraphs with no filler. The purpose is front-loaded, and every sentence adds value. It could be slightly more structured, but it is efficient.

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 12 parameters and no output schema, the description covers only a few parameters for a specific use case. Many common scenarios and parameter details are omitted, leaving gaps for an agent unfamiliar with the tool.

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 coverage is 0%, so the description must compensate. It explains the three critical parameters (i_know_what_im_doing, disable_coop, force_scope_access) and their importance, but leaves the other 9 parameters undocumented. This adds value but is incomplete.

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 first sentence clearly states the tool launches the Camoufox anti-detection browser, which is a specific verb+resource pair. This unambiguously differentiates it from sibling tools like close_browser, navigate, etc.

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 provides important parameter guidance for Cloudflare-style challenges but does not explicitly state when to use this tool versus alternatives. It implies the browser must be launched before other actions, but lacks when-not-to-use or exclusion criteria.

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