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

With no annotations, the description carries the full behavioral burden and does well: it discloses the pay-per-call cost ($0.001 USDC on Base) and, critically, that unpaid calls return a 402 challenge via x402/MPP. That is exactly the kind of context an agent needs to avoid spurious retries. It omits failure modes (non-HTML targets, timeouts, redirects) and payload-size limits, keeping it below 5.

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?

Two sentences, front-loaded with the core purpose and return payload, then the billing caveat. Zero filler and every 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?

For a one-parameter tool with no output schema and no annotations, the description effectively substitutes for a return schema by enumerating the metadata fields, and it covers the payment/auth flow. Missing only edge-case behavior (error responses other than 402, non-HTML pages), which is a minor gap.

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?

There is a single required `url` parameter with 100% schema coverage, which sets the baseline at 3. The description adds no semantics beyond that (no notes on absolute vs relative URLs, redirects, or whether the fetched resource must be HTML), so it neither helps nor hurts.

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+resource (fetch a web page) and enumerates the exact metadata categories returned: title, description, Open Graph, Twitter cards, canonical, JSON-LD. That is concrete and lets an agent know precisely what comes back. It is docked one point because it does not distinguish itself from the sibling `reader` tool, which likely also fetches page content.

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?

Usage is implied by the output description: use this when you want structured page metadata rather than raw content. However, there is no explicit guidance on when to choose this over the `reader` sibling, and no stated exclusions or prerequisites.

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