Solve a Cloudflare Turnstile or WAF challenge

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

Adds valuable behavioral context beyond annotations: tokens are single-use, expire in minutes, failed solves are never billed, and the tool needs SOLVEGATE_API_KEY. These lifecycle and billing details materially affect invocation and go beyond what readOnlyhew/openWorldHint/idempotentHint convey.

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?

Tightly written and front-loaded with purpose, then delivers the parameter nuance, token lifecycle, and billing policy in sequence. No filler or redundant repetition of schema content.

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 and rich annotations, the description supplies the remaining operational context: API key requirement, token lifecycle, failure billing, and host-binding constraint. An agent has enough to select and call this tool 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?

Although all parameters are already described in the schema, the description adds meaningful semantics: it explains when each `gate` value applies, why the URL must be the real rendering page, and why sitekey/url are both required. It does not add details for proxy or action, but those are adequately covered in the schema.

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 ('Clear') and resource ('Cloudflare challenge') plus the token output. It clearly identifies the two gate flavors but does not explicitly distinguish this tool from sibling tools like inspect_page or get_solve, which is the only thing preventing a 5.

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?

Provides clear context for choosing gate=turnstile vs gate=waf, and explains the URL must be the actual page where the challenge renders because sitekeys are host-bound. It does not explicitly state when not to use this tool or compare it to siblings, so it falls just short of full guidance.

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