page_captcha_rotate

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

With no annotations, the description carries the full burden, and it delivers: it discloses the brute-force JS-click sweep, the feedback keyword check, the human-replay phase, the approximate duration (~30s), the JSON return shape, and the convergence caveat. Nothing in the text contradicts the absent annotations.

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?

Three dense sentences front-load the tool's purpose ('brute-force sweep + human replay') and each subsequent clause adds new information (keywords, timing, return shape, caveat) without repetition.

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?

Covers the execution flow, return value, and a limitation, which is strong for a captcha solver. It stops short of telling an agent what status values can be, what happens on sweep failure, or how session_id/page_id/reset_ref factor in, so it is not fully complete for a 6-parameter tool.

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 already describes check_ref, reset_ref, rot_left_ref, and rot_right_ref; the description adds only the 15deg standard but does not clarify session_id, page_id, or how refs relate to the stated replay flow. At 67% schema coverage, the description does not fully compensate for the undocumented 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?

Opens with 'ROTATE CAPTCHA SOLVER' and immediately defines the challenge type ('turn an image upright'), which differentiates it from OCR, slide, and hCaptcha siblings. The sequencing detail (sweep then human replay) makes the verb/resource unambiguous beyond the name alone.

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 a clear trigger condition: rotate challenges that respond to 15deg-per-click buttons and a check button. It does not name explicit exclusions or alternative captcha tools, so it misses the top bar of the rubric, but the context is enough to route an agent correctly.

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