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

Goes well beyond the readOnly/openWorld/idempotent annotations: discloses robots.txt compliance, the lack of JavaScript execution, a precise pricing model ($0.003 per successful call, x402 USDC on Base), and the fallback behavior of returning a PaymentRequired object when called unpaid. This is exactly the operational context an agent needs before invoking a paid, open-world scraper.

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 usage trigger and then packed with high-value facts in two dense sentences – no filler. Slightly overloaded with stacked clauses (output fields, robots.txt, JS limits, pricing) in the second sentence, but each clause earns its place.

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 compensates by naming the returned fields (Markdown body, title, byline, publish date, language, word count) and the output format choice. Combined with the payment and rendering constraints, an agent has everything needed to call it correctly.

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 all five parameters are already documented in the schema, and the description adds little beyond mentioning Markdown/plain text output ('format'). The links, images and maxChars options are not elaborated in the description text. Baseline 3 applies.

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 ('read one public web page') plus the exact transformation (live fetch → clean Markdown/plain text with boilerplate removed). The scope ('one public web page') clearly separates it from the sibling tools feed, links, meta and sitemap.

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?

'Use when you need to read one public web page' gives clear triggering context, and 'Server-rendered HTML only (no JavaScript execution)' is an explicit exclusion. It stops short of naming the sibling tools as alternatives for feeds, links or sitemaps, so routing is inferred rather than stated.

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