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

Annotations already declare the operation read-only and idempotent, and the description adds material behavior beyond that: it discloses a real cost (x402 micropayment, 0.01 USDC on Base), the impersonation technique, and the feature of detecting anti-bot challenges. No annotation contradiction exists.

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 the core purpose, then gives the cost and usage guardrails, then lists parameters. Every sentence carries useful information, and the parameter list is a compact summary rather than prose padding.

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 two-parameter tool with a full input schema, output schema, and safety annotations, the description covers purpose, cost, selection criteria, and exclusions. The only minor omission is the payment mechanism, but the cost and requirement are clearly stated and not needed to form the call.

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 parameters. The description mostly restates the schema ('url' as target webpage, 'custom_headers' as additional headers) without adding format, precedence, or interaction semantics, which keeps it at the baseline.

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 names a specific verb and resource (fetch webpage HTML) and adds a distinctive purpose: bypassing bot protection via browser TLS/header impersonation, which separates it from generic readers like read_web_page and extractors like extract_json_from_web. The 'When to use' mention of 403s further clarifies the intended niche.

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 gives explicit when-to-use (sites returning 403 to standard clients) and when-not-to-use (downloading large binaries). It does not name sibling tools as alternatives, so it stops just short of the top anchor.

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