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

Annotations cover safety flags but say nothing about billing or failure behavior; the description fills that gap with per-call pricing, the crucial 'charged per successful solve' rule, refund of reserved funds on failed/empty attempts, and the proxy/IP-binding caveat for certain types. This is exactly the beyond-annotations context an agent needs before spending money.

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?

Front-loaded with the core action, then cost, then when-to-use, then the prerequisite — a sensible priority order. The dollar-range and refund parenthetical is dense, and the mixed-language/asterisk emphasis slightly clutters it, but nearly every clause earns its place.

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, so the description carries the return burden and does so by promising 'a ready-to-use solution'. Combined with pricing, failure semantics, and the cross-type param routing, an agent has everything needed to invoke this correctly.

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 100% and the type enum is self-explanatory, so the baseline is 3; the description adds real value by explaining that the params object is type-dependent and by flagging the subset of types that require the caller's own proxy because delivered cookies are IP-bound. It still doesn't name per-type param fields, hence not a 5.

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?

States a specific verb and resource ('Solve a CAPTCHA or bot challenge and get a ready-to-use solution') and immediately differentiates itself by noting that params vary per type and that everyinfra_list_captcha_types must be consulted first. An agent can distinguish this from query/billing/key siblings without opening any schema.

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?

Gives an explicit when-to-use trigger ('when a target site is blocked by Turnstile / reCAPTCHA / hCaptcha / a Cloudflare challenge page / GeeTest') plus the concrete prerequisite: check params with everyinfra_list_captcha_types first. Names both the condition and the sequencing step.

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