browser_solve_captcha

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

No annotations provided, so description carries full burden. It describes the process but omits behavioral details like rate limits, costs, timeouts, or what happens on failure. The dependency on env vars (CapSolver/2Captcha) is mentioned but not explained.

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 sentence that efficiently conveys the main workflow. It is clear and front-loaded with the tool's role, though slightly dense with multiple clauses.

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?

No output schema exists, but description does not explain return values (e.g., success flag or token). Input parameters are well-covered. Absence of failure/error handling info and provider configuration details makes it adequate but not complete.

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 100%; the description adds little beyond schema descriptions (e.g., 'Override auto-detection' for type). Baseline 3 applies as schema already documents parameters adequately.

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?

Description clearly states the tool is a fallback captcha solver for Turnstile/hCaptcha/reCAPTCHA, with specific steps: detect, submit to provider, poll, inject. Verb and resource are explicit, and it is distinct from all sibling browser 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?

The term 'fallback' implies usage when other methods fail, but no explicit guidance on when to use this tool versus alternatives, nor when not to use it. No mention of prerequisites like provider configuration beyond env var names.

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