nex_captcha_query

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

Discloses behavior beyond the annotations: FAILED/EXPIRED are refunded server-side, billing should be verified, network errors and unknown states are not failures, and no cancellation or manual refund exists — which explains why readOnlyHint is false despite the 'query' name. This is exactly the side-effect context an agent needs.

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-loaded with the action and cadence, and every clause carries operational meaning. It is dense and semicolon-chained rather than cleanly separated, which slightly hurts scannability.

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?

With no output schema, the description covers the shape of 'solution' (text, token, or product-specific fields) and all terminal states, which is what an agent needs to interpret results. Minor gaps remain on intermediate states and error payload shape.

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 0% and the single parameter has no description, but the prose compensates by specifying that the id is the local CAPTCHA record id rather than the upstream taskId. That resolves the main ambiguity, though it gives no format/range detail.

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 and resource ('Query one local CAPTCHA record id') and explicitly disambiguates the identifier from the upstream taskId, which prevents confusion with the buy/record-list siblings. An agent can tell exactly what object this operates on.

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 concrete polling guidance (every 3–5 seconds, max 5 calls per 3 seconds), explicit terminal conditions (SUCCEEDED, FAILED, EXPIRED), and states there is no cancel or manual refund path. That is explicit when/when-not behavior rather than implied usage.

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