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

Annotations already establish readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable context beyond that: the $5 USDC cost, the refund-guarantee condition tied to retries=3, and the 50% discount for batch calls. These payment and failure-behavior details are meaningful and not present in the annotations. No contradiction with the readOnly hint, since scraping is a read operation.

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 compact, front-loaded with the core purpose, and organized as a scannable three-item list. The promotional tone ('3x Features', '$5 USDC') adds a little noise, but no sentence is wasted. It earns its space efficiently.

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?

An output schema exists, so return values are covered externally, and all params are documented at 100% coverage. The description explains the three headline features well. However, it omits the payment mechanics around the wallet param, any rate-limit or concurrency constraints for batch calls, and the conditions under which the refund guarantee actually applies. These gaps matter for a paid tool with 0 required parameters.

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 all five parameters are already documented with their own descriptions. The description adds some extra semantics (50% discount for urls, refund guarantee for retries=3, JSON output for extract), which is genuinely useful above the schema. But the wallet parameter's role is left unexplained in both the description and schema beyond 'your wallet address', and the marketing framing adds little technical meaning. Baseline 3 is appropriate.

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 opens with a clear core capability ('Bypass enterprise bot walls') and the name carries the scrape verb, so an agent can tell this is a stealth web-scraping tool. The three features (extract, retry, batch) clarify what it does. However, it doesn't explicitly differentiate from sibling scrape.bypass_captcha, which also deals with bot-wall circumvention, leaving some ambiguity about which to pick.

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 lists features but gives no when-to-use guidance and no comparison against alternatives. Siblings like scrape.bypass_captcha and scrape.to_json overlap in domain, yet no condition is given for choosing this tool over them. The only implicit usage signal is the 'bypass bot walls' phrase, which is too weak to route an agent reliably.

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