wait_for_captcha

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

With no annotations provided, the description must carry the full behavioral disclosure burden. It states that the tool waits up to timeout_ms, but does not explain what happens on timeout, whether it returns as soon as the CAPTCHA is solved, whether it fails if no CAPTCHA is present, or what the response looks like.

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?

The description is a single compact sentence that front-loads the core behavior and directly references the only parameter. Every word earns its place, with no filler or unnecessary detail.

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 tool is simple, but there is no output schema and no annotations, so the agent is left without key contextual details like return values, timeout results, and whether the tool assumes a CAPTCHA has already been detected. The description is not complete enough for an agent to confidently predict the tool's full behavior.

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 0%, so the description needs to compensate. It does connect timeout_ms to the waiting behavior, indicating it is the maximum wait duration, but it adds little beyond the parameter name and does not explain timeout consequences or default behavior.

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 verb 'wait' and the specific resource 'the page's CAPTCHA', making the tool's primary function obvious. However, it does not explicitly differentiate itself from sibling tools like detect_captcha or wait_for, so it stops short of 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?

The description provides no guidance on when to use this tool versus alternatives such as wait_for, wait_for_load, or detect_captcha. There is no mention of prerequisites like having already detected a CAPTCHA, nor any exclusionary context.

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