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

Annotations declare readOnlyHint=true, destructiveHint=false, and idempotentHint=false, so the safety profile is covered. But the description adds no behavioral color: it does not disclose the paywalled nature of the operation (implied by the 402 price-quote parameter), the non-idempotent repeat behavior, or the captcha-circumvention implication. It merely restates the title and output format.

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 efficient sentence with zero wasted words and the primary purpose front-loaded. It is appropriately sized for the simplicity of the tool, though the brevity borders on under-specification.

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 tool with a payment mechanism and behavioral quirks (non-idempotent, captcha bypass), the description is incomplete. While an output schema exists, there is no usage context, no pricing/payment disclosure, and no differentiation from the scrape siblings—an agent lacks critical routing and expectation-setting information.

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 the schema already documents both url and paymentProof well, including the 402-quote fallback. The description adds nothing about parameters beyond what the schema provides, so the baseline 3 applies.

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 states a clear verb+resource (bypass captcha on a webpage) and a specific output format (clean Markdown), which distinguishes it from the JSON output of sibling scrape.to_json. However, it never names the sibling tools or explicitly states what it is not, so it falls short of full differentiation.

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?

No guidance is given on when to use this tool versus scrape.to_json, scrape.stealth_residential, or analysis.summarize_clean. The description offers no context about selection criteria, exclusions, or prerequisites—an agent must infer everything from the name and schema.

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