solve_captcha

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does an excellent job: it explains the stealth mechanism (CDP vs JavaScript, avoiding isTrusted: false), automatic coordinate detection, the lack of guarantee of success, limitations with shadow DOM, and potential side effects (changes to page state or cookies). It also outlines the return message and its non-guarantee. This is comprehensive and honest.

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 well-structured with sections and a numbered workflow, which aids readability. It is somewhat lengthy but every sentence adds value: it covers purpose, stealth, detection, limitations, workflow, and return value. It is front-loaded with a clear purpose statement, and the workflow steps are concise. The length is justified by the need to explain complex behavioral nuances.

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 simplicity (0 parameters), the absence of annotations, and the existence of an output schema (which the description aligns with), the description is complete. It explains what the tool does, how it works under the hood, its limitations, and how to integrate it into a broader workflow. An agent has all necessary information to invoke it correctly and understand its outcome.

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 tool has zero parameters by design, so there are no parameter semantics to describe. However, the description compensates by explaining what the tool does automatically (detects coordinates, no need for manual input). Since schema coverage is 100% but empty, the description adds value by clarifying that no arguments are necessary and that behavior is determined by page context. This is above the baseline for zero parameters.

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 clearly states the tool attempts CAPTCHA interactions via CDP, listing specific CAPTCHA types (Cloudflare Turnstile, reCAPTCHA, hCaptcha, DataDome Slider, FriendlyCaptcha) and actions (click, drag/drop). It distinguishes itself from simpler JavaScript actions by emphasizing stealth, and from other tools like 'click' by focusing on CAPTCHA-specific automation. The purpose is unambiguous and well-scoped.

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 an explicit workflow: first inspect with get_content, then call solve_captcha, then verify with get_page_info or check_condition. It names specific sibling tools for pre- and post-conditions, and states when not to use (if no CAPTCHA is detected, no action is performed). This gives clear guidance on when and how to use the tool, and what to do after.

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