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. The word 'attempt' honestly signals possible failure, but the description does not explain side effects, waiting behavior, external dependencies, prerequisites, or what happens if solving fails. For an action tool with no annotation coverage, this is a significant gap.

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 concise sentence with no filler or redundancy. It front-loads the action and resource while adding a useful concrete example in parentheses, making it immediately scannable.

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?

Captcha solving is a complex, potentially non-deterministic operation, and with no annotations or parameter schema to carry context, the description should explain expected behavior more thoroughly. It does not mention timeouts, possible failuire modes, whether the agent should wait for the captcha to appear first, or how to verify success. The presence of an output schema reduces the need to describe return values, but operational context is missing.

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 and the schema coverage is 100%, so the description has no parameter information to add. Since there are no inputs, the baseline of 4 applies and the high-level reference to 'on the page' is sufficient context.

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 action ('solve') and the resource ('a captcha on the page'), and gives a concrete example ('Cloudflare Turnstile'). It is distinct from sibling tools because none of them address captchas, but 'attempt' leaves some ambiguity about exactly what mechanism or outcome is involved.

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 implies usage when a captcha is encountered on the page, and the example names a common scenario. However, it provides no explicit guidance about when not to use it, what to do after solving, or how to handle failure.'

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