scrape_html_headless_fallback

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

With no annotations provided, the description carries the full burden. It usefully discloses the two-tier execution flow (fast static parse, then headless Chromium fallback) and the 0.02 USDC settlement cost on Base L2. However, it omits what happens when both tiers fail, the output/return format, timeouts, or whether payment is mandatory on every call.

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?

One tightly packed sentence with the core strategy front-loaded and cost relegated to a parenthetical. Every element earns its place; there is no filler or restatement of the tool name.

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?

A payment-requiring, fallback-capable tool with no output schema and no annotations demands more context. The description neither explains what the tool returns (HTML content? status codes? errors?) nor what happens on failure, and it leaves the payload input undefined. The dual-tier behavior alone is insufficient for correct invocation.

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 100%, so the baseline is 3. The description adds no parameter-level meaning beyond what the schema already provides: it does not clarify what the payload should contain (URL, raw HTML, options) or the expected paymentSignature format beyond the schema's generic 'x402 settlement' wording.

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?

States a specific verb and resource (scrape HTML) and a distinctive dual-tier strategy: static parse first, headless Chromium fallback only when JS hydration is needed. This makes the tool's function clear and sets it apart from related siblings like html_clean_boilerpipe_extractor, though no sibling is explicitly named.

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 explicit guidance on when to use this tool versus alternatives. The phrase 'only if JS hydration is required' hints at the triggering scenario, but there are no exclusions, prerequisites, or comparisons to competitors like resilient_http_probe. An agent must infer the selection criteria from the sibling names alone.

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