wait_for_bot_wall

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

With no annotations, the description carries the full burden and delivers: it polls while auto-verifying, runs the configured solver for user-required challenges, presses the checkbox if needed, and enforces a hard limit ('image puzzles are never solved'). Failure behavior (structured verdict) and side-effect (checkbox press) are disclosed.

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?

Front-loads the core action, then layers in the captcha-before-submit case and the handoff rule. It is dense and long, but each sentence contributes distinct behavioral information rather than restating the name.

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?

There is no output schema, and the description compensates by describing the return shape ('structured verdict', 'reports whether a token was issued'). Combined with the parameter context this is nearly complete, though it could say a bit more about the verdict's fields.

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 75%, with defaults and meanings already documented on max_wait_ms, apply_solver and poll_interval_ms. The description reinforces these by referring to the 'wait budget' and the 'configured solver', adding contextual meaning for how the parameters interact without contradicting the schema.

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?

States a specific verb+resource ('wait out a bot wall on a tab, then attempt to solve it') and goes further by naming the concrete scenarios (Cloudflare 'Just a moment…', embedded Turnstile/reCAPTCHA/hCaptcha). None of the sibling browser_* tools handle bot walls, so an agent can distinguish it immediately.

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 explicit when-to-call conditions: before submitting a form with an embedded captcha widget, and whenever a bot wall may auto-clear. It also states when to stop and hand off to the user vs continue, which is exactly the routing decision an agent needs.

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