captcha_wait_for_resolution

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

The description discloses key behavioral traits: it blocks until resolution or timeout, which is essential for an agent to understand the tool's impact. Without annotations, the description carries full burden, and it adequately conveys the blocking nature and timeout behavior, though it could mention implications like thread blocking or error handling.

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?

Two concise sentences: the first states the core blocking behavior, the second gives a usage context. Front-loaded with essential information and no unnecessary words.

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 tool's simplicity (3 params, no output schema, no annotations), the description covers purpose and usage adequately. It could be improved by noting the return value (e.g., resolution details) or clarifying timeout behavior, but it is largely complete for an agent to use the 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?

Schema coverage is 100%, meaning each parameter is already described in the schema. The tool description does not add any extra meaning or context beyond what the schema provides, so per the guidelines, a baseline of 3 is appropriate.

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 blocks until human intervention is resolved or timeout expires, with a specific verb (block/wait) and resource (human intervention/captcha resolution). It distinguishes itself from sibling tools like captcha_request_human_intervention (initiates) and captcha_resolve_intervention (resolves) by focusing on waiting.

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 explicitly says 'use this to pause automation while waiting for human to solve captcha,' providing clear guidance on when to use the tool. However, it does not mention when not to use it or discuss alternatives (e.g., captcha_handle_auto), which would strengthen guidance.

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