Browser Captcha Solve

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

With no annotations, the description carries the behavioral burden. It discloses that automatic solving requires an external provider key and which captcha types are supported, but it does not explain side effects such as whether it submits the page, how it waits, possible failures, or rate/cost implications of calling an external service.

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 concise and front-loaded: the core action is stated in the first sentence, and the following lines add requirements and supported types without repetition or filler.

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 output schema is present, not explaining return values is acceptable. The main gaps are parameter semantics (tab/session/provider) and lack of usage context versus siblings, making it only partially complete for a tool with four optional parameters and no annotations.

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 description coverage is 0%, so the description must explain the four parameters. It only hints at 'ref' for plain image captchas and indirectly at 'provider' via the key names; 'tab', 'session', and the meaning/range of 'provider' are left undocumented. This does not compensate for the schema gap.

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 states a clear action on a specific resource: 'Solve the captcha on the current page automatically.' It further specifies supported captcha types (reCAPTCHA v2, hCaptcha, Turnstile, plain image), which distinguishes it from sibling tools like browser_captcha_detect and browser_captcha_manual_wait.

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 gives useful context: use it to solve the current page's captcha automatically, and it needs a provider API key. However, it never names alternatives or states when not to use it (e.g., when manual approval is required, use browser_captcha_manual_wait), so the guidance is implied rather than explicit.

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