challenge_wait

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

With no annotations provided, the description carries full burden and does well: it discloses polling behavior, timeout, that it waits until interstitial disappears, and that headed Chrome lets passive challenges finish. This covers key behavioral traits without implying destructiveness or mutations.

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 sentences, both essential: first defines action/timeout, second adds browser-specific behavior. No fluff, front-loaded purpose, every word adds value.

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 no output schema, the description is fairly complete: it explains what triggers completion (disappearance of interstitial), timeout behavior, and a browser nuance. Could optionally mention return value or success signal, but for a polling/wait tool with optional params, this is adequate.

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%, so baseline is 3. The description adds no parameter details beyond what the schema provides; both 'timeoutMs' and 'intervalMs' are fully described in the schema with defaults. The description does not add extra semantic context.

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 identifies the purpose: polling until a Cloudflare-style interstitial disappears, with timeout. The verb 'poll' and resource 'page' are specific, and it distinguishes from siblings like 'human_wait' or 'browser_wait_for' by mentioning 'Cloudflare-style interstitial'.

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 implies when to use (when a challenge interstitial is present) but lacks explicit when-not-to-use or alternatives. Siblings like 'human_wait' or 'captcha_detect' exist but are not mentioned as alternatives. No guidance on prerequisites.

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