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

Goes well beyond the annotations by disclosing the cost model ($0.002 USDC per request), the x402 payment/auth requirement, rendering limitations (HTML only, no JS, no login), the returned fields, and a security warning that page links are untrusted. The payment side effect is what makes readOnlyHint=false coherent rather than contradictory, and the description explains it.

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 tightly packed sentences with purpose, scope, alternatives, cost, and a safety note; the core purpose is front-loaded. Slightly weakened by the unused 'FetchDelta:' prefix and by stacking three facts (HTML-only, no JS, no login) without much flow.

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, yet the description itemizes the return contents, and with annotations present the safety/behavior profile is largely covered, so an agent can call it confidently. Missing only failure behavior (e.g. what happens for JS-dependent or non-HTML pages) and explicit parameter docs.

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 0% for the single 'urls' parameter, so the description carries the burden. 'One public web page' hints that only a single URL is accepted (matching maxItems=1) and that it must be publicly reachable, but it never explains the array-of-URLs shape or the 2048-char URI constraint.

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 one public web page as Markdown') plus the return contents (title, headings, links, timestamp), so an agent knows exactly what it does. It gestures at sibling differentiation by referencing the free preview alternative, but never names preview_page, and the description opens with 'FetchDelta:' while the tool is actually named 'resolve', which muddies identity.

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?

Gives concrete when-to-use guidance ('current docs, changelogs or policy text') and explicit limits ('HTML only; no JavaScript rendering or login'), plus a routing cue: preview readability for free before paying. It stops short of naming the preview_page sibling or stating when this tool should not be chosen over catalog/diff/page_watch.

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