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

With no annotations, the description carries the full load and does real work: it discloses that no LLM or API key is needed, a ~1s latency, a $0.01 USDC-on-Base price, and that payment goes in params._meta["x402/payment"] via x402. That is exactly the kind of auth/cost disclosure an agent needs before calling. It stops short of failure modes, rate limits, JS-rendered page behavior, or paywalled/robots-restricted pages.

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?

Front-loaded with the capability and return payload, then operational facts (no LLM, no key, ~1s), then cost and transport. The return-type enumeration is long but every item maps to a real mode, so it earns its space; only the raw HTTP endpoint line is arguably redundant for an MCP caller.

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 4-param, no-output-schema, no-annotation tool this covers the essentials: what it returns, that it is cheap and fast, and critically how to pay. Missing pieces are secondary — error/partial-fetch behavior, JS rendering, and how the limit interacts with mode — but none block a correct first 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 baseline is 3; the description earns above that by revealing the x402 payment payload in params._meta, which is not documented in the input schema at all and is essential to a successful call. It also implicitly maps the returned artifacts to the mode enum. It adds nothing about limit bounds or same_domain_only beyond the schema.

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 ('Fetch a public web page') and enumerates exactly what comes back (title, outline, article text, markdown, links, images, tables, JSON-LD), so the agent knows the shape of the result without opening a schema. It does not, however, distinguish itself from close siblings like webread__read, webread__outline, web_extract__extract or webmd__extract, which is the remaining gap.

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?

Usage is only implied: it is obviously for reading a public page, and the payment/endpoint lines give operational context. There is no explicit when-to-use vs when-not, and no named alternative among the several overlapping extraction siblings, so the agent must infer selection.

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