Solve GeeTest v3

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

No contradiction with annotations (readOnlyHint=false, destructiveHint=false). Description adds valuable behavioral context beyond annotations, such as single-use challenge expiry, the need for immediate fetching, and that results should be posted back like the site's own front-end. This enhances transparency about failure modes and usage constraints.

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?

Description is three sentences, front-loaded with the core action and return values. It includes an important usage warning without unnecessary elaboration, making every sentence purposeful.

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 six parameters, output schema, and annotations, the description covers the key operational context: what the tool solves, what returns, and the critical freshness requirement. It does not discuss proxy usage or timeout, but those are well-documented in the schema, so the description is sufficiently complete for typical use.

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%, with detailed descriptions for all 6 parameters. The description reinforces the challenge freshness warning and gt reuse but adds minimal new meaning beyond the schema. Baseline of 3 is appropriate since the schema does the heavy lifting.

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 'Solve a GeeTest v3 slide-puzzle captcha', naming the specific captcha type and resource. It also specifies return values (geetest_challenge, geetest_validate, geetest_seccode), distinguishing it from sibling captcha-solving tools like reCAPTCHA and Turnstile.

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 explicit operational guidance: 'fetch gt and challenge from the page immediately before calling' and warns that a stale challenge is the most common failure. It does not explicitly contrast with alternative siblings, but the captcha-type-specific name and description give clear context for when this tool is appropriate.

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