Cloud browser automation (Browser API)

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

Without annotations, the description carries the burden and does a good job: it discloses that the tool runs on Bright Data's remote infrastructure, requires auth, supports automatic CAPTCHA solving and sticky sessions, and can return HTML, text, and/or screenshots. It does not mention rate limits, costs, or side effects on live sites, but these are less critical given the explicit interaction features.

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?

Two dense but well-structured sentences cover the tool's purpose, capabilities, infrastructure, and authentication requirement. There is no fluff, and every clause adds useful information.

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?

For a complex tool with no annotations and no output schema, the description covers the essential behavioral surface: target use case, interaction types, output formats, infrastructure, and auth. It omits details on error handling and rate limits, but the schema fills in defaults for many parameters.

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 58%, and the description compensates by mapping capabilities to parameters: 'automatic CAPTCHA solving' (solve_captcha/captcha_timeout), 'ad blocking' (block_ads), 'device emulation' (device), 'sticky sessions' (session_id), 'clicks/typing/scrolling' (actions), and output types (return_html/return_text/screenshot). It does not explain wait_until/nav_timeout, but the schema provides enums and defaults for those.

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 the specific verb 'Drive' and identifies the precise resource: a 'real, remote cloud browser (Puppeteer over CDP).' It explicitly scopes the tool to JavaScript-heavy sites and multi-step flows, and enumerates unique capabilities (CAPTCHA solving, ad blocking, sticky sessions) that distinguish it from sibling scraping tools.

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?

It clearly identifies target use cases: JavaScript-heavy sites and multi-step flows. It also notes the prerequisite that BRIGHTDATA_BROWSER_AUTH must be set, effectively telling the agent when it can be used. However, it does not explicitly name alternatives or state when not to use it, so it stops short of a 5.

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