nex_browser_captcha_complete

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

The annotations say only readOnlyHint=false and idempotentHint=false. The description adds substantial context beyond that: it discloses clicks with real consequences, that repeat calls only inspect progress and never click again, that a changed Grid returns a nextPrepareId without charging, and that an unclear charge blocks new charges. The billing and retry semantics are genuinely useful, though phrases like 'Website acceptance needs page evidence' remain opaque.

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 text is dense but not bloated, and most sentences cover required workflow ground. The problem is ordering: it begins mid-flow with an instruction instead of leading with what the tool does, and the long compound sentences make failure, billing, and page-evidence rules hard to scan.

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?

For a multi-round, stateful workflow with no output schema, the description covers a fair amount: task states (SUCCEEDED/FAILED/EXPIRED), the nextPrepareId handoff, the attempt cap, and charge-blocking behavior. It leaves out what the tool actually returns to the caller, the source of prepareId, and what 'page evidence' and 'final sign-up/login button' mean operationally.

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?

There is one required parameter, prepareId, at 0% schema description coverage, so the description carries the burden of explaining it. It never defines prepareId directly; only the phrase 'A changed Grid returns nextPrepareId... submit it as the next round' hints at the value's origin and that it can be replaced between rounds. That is a thin, indirect substitute for documenting the parameter.

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 opens with a procedural step ('Query the task once; on SUCCEEDED apply the answer...') rather than a plain statement of what the tool is: the step that finalizes a captcha challenge inside the browser. The verb and resource are inferable from the workflow narration, but with siblings named nex_browser_captcha_prepare and nex_browser_captcha_submit, the definition never explicitly differentiates this completion step from those two.

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?

It gives solid procedural guidance for a run already in progress (poll pending tasks every 3-5 seconds, treat a changed Grid as a new round, stop after 3 attempts on FAILED/EXPIRED). What it never states is when an agent should choose this tool rather than nex_browser_captcha_submit or nex_captcha_query, nor the precondition that a prepare call must already exist.

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