solve_captcha

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

With no annotations, the description carries the full burden, yet it never says this is a mutating operation that types into fields, may click refresh buttons, and can submit the form (the `submit` param defaults to false but can trigger navigation). It discloses nothing about required page state, failure behavior after `maxRetries`, or what is returned, all of which matter for a 19-parameter side-effecting tool.

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 tight sentences with the capability list front-loaded and no filler. It is arguably undersized rather than overly verbose for a tool this broad.

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 19-parameter tool with nested objects, no output schema, and no annotations, the description leaves key questions unanswered: what it returns (answer text, filled form, status), what happens when all retries fail, and whether the page must be pre-navigated. It is minimally viable but not sufficient on its own.

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 95%, so the baseline is 3; the description's mention of 'JavaScript-based challenge widgets, image text transcription, and intelligent form field mapping' loosely maps to the `type`, `lang`, and `aiMatch`/`formData` params but adds no new semantics like selector precedence or how `auto` detection resolves.

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 action set: automate form completion and interactive widget verification, covering JS widgets, image text transcription, and field mapping. The verb+resource is clear, though the description never uses the term 'captcha' that the tool name and `captchaSelector` imply, and it does not differentiate from siblings such as `type`, `click`, or `extract_data`.

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 names intended contexts (QA, automated browsing workflows) which implies when to reach for it, but gives no explicit when-not-to-use and no mention of the alternative of driving forms manually via `type`/`click` or of prerequisites like an already-loaded page.

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