solve_on_page

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

With no annotations, the description carries the full burden and largely succeeds: it discloses the headless browser flow, CapSolver API, DOM injection, configurable defaults, and the success/error return structure. It omits secondary details such as needing an API key or behavior with zero captchas, but the core behavioral model is clear.

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 front-loaded with a clear summary, followed by a compact operational flow, a single dependency note, and tidy parameter and return sections. Every sentence adds value and there is 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?

For a complex browser-automation tool, this description covers the workflow, prerequisites, parameters, and expected returns well. It falls just short of complete by not mentioning environment requirements like CapSolver API credentials or behavior when no captcha is found, but the missing pieces are secondary.

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 prose must explain every parameter. It does: page_url is defined, autofill's behavior and default are given, and timeout and polling_interval specify units and defaults. An agent can set each parameter confidently without additional schema descriptions.

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 first sentence uses specific verbs and a resource: 'Detect, solve, and optionally autofill all captchas on a page.' This clearly identifies the operation and distinguishes it from siblings like detect_captchas and solve_captcha by describing a single page-wide flow.

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 implies the use case with 'one-shot operation' and 'all captchas on a page', but it does not explicitly name alternative tools or state when not to use this tool. The playwright prerequisite is helpful, but 'when to use vs alternatives' is only inferred.

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