solve_captcha

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It mentions 'using configured captcha service' but does not explain what that configuration entails, whether the tool blocks until solved, or how failures are handled. Key behaviors are missing.

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 sentence with no waste. It is concise, though slightly more structure (e.g., separating prerequisite from action) could improve clarity. Still, it efficiently conveys the core purpose.

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?

Given the tool has 2 parameters, no output schema, and no annotations, the description is incomplete. It lacks information about prerequisites (e.g., must have a captcha detected via 'detect_captcha'), error conditions, or expected outcome. More details are needed for safe autonomous use.

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 100%, so baseline is 3. However, the description adds no additional meaning beyond the schema's parameter descriptions: sessionId is required and apiKey is an optional override. The description does not provide further context such as constraints or expected values.

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 clearly states the tool's action: 'Solve a detected captcha on the current page using configured captcha service'. It uses a specific verb 'Solve' and resource 'captcha', and distinguishes itself from sibling tools like 'detect_captcha' and 'solve_2fa'.

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 usage after a captcha is detected ('detected captcha') but does not explicitly state when to use versus alternatives or provide exclusions. No explicit usage guidance is given.

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