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

With no annotations, the description carries the full burden and does well: it discloses that boilerplate/scripts/navigation are stripped, that no API key or account is required, and that each call costs $0.01 via x402/USDC. It omits failure behavior (timeouts, 404s, paywall handling) and any rate limits, which leaves a gap for an operation that can fail in many ways.

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 what the tool returns, then scoping, then cost and auth. Every sentence carries distinct information (output shape, stripping behavior, intended iteration pattern, pricing) with no filler.

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?

No output schema exists, so the description must describe the return value, and it does so field by field, alongside cost and auth requirements. For a two-parameter read tool with no annotations, nothing an agent needs in order to call it correctly is missing.

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 url (http/https only, no private/loopback) and links (defaults to false), making 3 the baseline. The description adds little parameter-level syntax beyond noting that links carry their destinations, though that phrasing slightly blurs the distinction with the boolean links parameter.

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 ('Fetches one URL and returns the readable page as markdown') and enumerates the return contents (title, description, headings, paragraphs, links, canonical URL, language, word count). This clearly separates it from the sibling web_status, which only probes availability.

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?

'Built for going through a list of links one at a time' gives clear context for when this tool is the right one (single-page reads, iterating over links) rather than a crawl. It does not explicitly name or exclude alternatives such as web_status, so it stops short of a full when/when-not statement.

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