tor_get_captcha

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

With annotations already indicating read-only and non-destructive behavior, the description adds useful behavioral context: it attempts local OCR as a hint and emphasizes the agent's vision as the primary reading mechanism. No annotation contradiction is present.

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 concise sentences front-load the core purpose, mention the OCR hint, and provide the follow-up action. Every sentence earns its place with no filler or redundancy.

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?

The description covers the return type (image), OCR hint, and workflow, but leaves the selector parameter undefined and doesn't describe possible failure modes or return format details. For a simple read-only tool, it's adequate but has clear gaps.

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 single required parameter `selector` is never explained in the description. Schema description coverage is 0%, so the description must compensate, but it provides no guidance on how the selector should be specified (e.g., CSS selector for the CAPTCHA element).

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 tool captures a CAPTCHA image and returns it for the agent to read, distinguishing it from sibling tools like tor_screenshot_element (generic element screenshot) and tor_solve_captcha (automatic solving). The verb 'Capture' and specific resource 'CAPTCHA image' make the purpose unmistakable.

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 gives clear context on when to use the tool ('Primary strategy: YOU read the image') and instructs the next step ('After reading, call tor_type to fill in the answer'). It doesn't explicitly name alternatives or exclusions, but the usage context is well-defined.

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