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

No annotations, so the description carries the full burden. It usefully discloses the SSRF guard and that raw HTML (not parsed text) is returned, but is silent on timeouts, response size/truncation, redirects, and whether JavaScript is executed before capture — meaningful behavioral unknowns for a network fetch.

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?

A single front-loaded sentence with an em-dash qualifier; the resource, payload, and differentiator all appear before any trailing clause. 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?

With no output schema, the description correctly specifies the return value (raw HTML source) and a key safety property. What remains missing — size limits, timeouts, rendering behavior — is secondary for a simple one-parameter fetch tool.

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?

One parameter with 100% schema description coverage, so the schema already documents 'url'. The description adds only the constraint that it must be public (SSRF-guarded), which is modest added meaning 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 (fetch) and resource (a public URL) plus the exact payload returned (full raw HTML page source). The clause 'not just extracted text' actively distinguishes it from siblings like x402-text-scrape, x402-web2md, and x402-html-text-extract.

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 a clear selection criterion — use this when the complete page is needed rather than extracted text — which implies its position relative to the text-extraction tools. It stops short of naming an alternative tool or stating exclusions (e.g. no JS rendering, public URLs only).

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