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

Annotations already cover readOnly and openWorld, so the bar is lower, and the description still adds real value: it discloses content stripping of scripts/navigation/boilerplate, the exact payload fields, and a per-call price of $0.005 USDC on Base via x402 — cost and payment protocol are critical for an agent to know before invoking. What it omits is failure behavior (JS-only pages, non-HTML content, what happens if payment is not set up) and whether return size is truncated.

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?

Four tight sentences with no filler: what it does, what it returns, what it removes, why it is useful, and what it costs. The most decision-relevant facts (scope and output shape) are front-loaded, with pricing correctly deferred to the end.

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?

With no output schema, the description properly compensates by enumerating returned fields, and it covers the payment model that annotations cannot express. It falls slightly short on error/edge-case behavior and how the x402 payment is actually settled, though the sibling x402_preflight may cover that.

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 schema already documents both url and maxChars, and the baseline of 3 applies. The description adds no detail on maxChars truncation behavior, and it does not flag that maxChars is typed as a string despite the documented default 20000 / max 100000.

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 any public web page') and enumerates exactly what comes back (Markdown of main content, title, meta description, word count, absolute links), so the tool is instantly distinguishable in intent. It does not explicitly contrast itself with siblings such as web_link_check or web_security_headers, which keeps it short of a 5.

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?

'Good for feeding pages to an LLM' is a benefit statement that implies the use case but gives no explicit selection criteria against the many other web_* siblings. There is no when-not guidance (e.g., JS-rendered pages, paywalled/authenticated pages) and no named alternative.

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