Browser Captcha Manual Wait

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

With no annotations, the description carries the behavioral burden. It discloses that the tool polls, waits, and requires a visible browser environment. It does not mention edge behavior such as whether timeout_s=null means it can block indefinitely or what happens when the timeout is reached.

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 efficient sentence that front-loads the purpose, then adds the environment prerequisite and polling behavior. Every clause earns its place with no filler or repetition.

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 has four parameters, no annotations, and no schema descriptions, but the description covers only the high-level behavior and environment requirement. An agent is left without parameter semantics or explicit routing between this tool and browser_captcha_solve, so the definition is not complete enough for confident selection and invocation.

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 must compensate for the four parameters, but it mentions none of them. tab, poll_s, session, and timeout_s are left to be inferred solely from their names and defaults, which is not enough for reliable invocation.

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 states a specific verb and resource: wait for a human to solve a captcha. It also gives the termination condition ('until the captcha disappears') and differentiates itself from automatic solve/captcha-detection siblings via the words 'manual' and 'human'.

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 a clear usage context: use this when a human is solving a captcha, and it requires a visible browser (NAVIGATOR_HEADLESS=false or VNC). It does not explicitly name alternatives like browser_captcha_solve, but the manual-vs-automatic distinction is strongly implied.

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