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

With no annotations, the description carries the full burden. It does disclose two valuable behavioral facts: it only works on public pages and it requires payment (0.01 USDC on Base / 12 sats Cashu / 12 sats Lightning). It says nothing about rate limits, JS rendering, robots.txt handling, redirects, or failure modes.

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 tight sentences with the return shape front-loaded and the payment terms second. The payment sentence is dense but each element earns its place since pricing is otherwise invisible to an agent.

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 and no annotations, the description compensates by enumerating the returned fields and disclosing the cost model, which is the minimum an agent needs to call it. The remaining gap is not knowing when this tool beats its overlapping siblings.

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 parameter with 100% schema description coverage ('Public http(s) URL'), so the schema already documents it. The description reinforces the public-URL restriction by saying 'public web page' but adds no syntax, normalization, or edge-case detail 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?

The description gives a specific verb+resource ('Fetch a public web page') and enumerates exactly what is returned (title, meta description, outbound links, plain text as JSON). However, it never distinguishes itself from close siblings such as meta, links, or readable_text, which appear to expose overlapping subsets of this output.

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?

There is no when-to-use guidance and no routing to alternatives, even though siblings like meta, links, readable_text, and markdown plausibly cover the same ground. The only usage-relevant detail is the payment requirement, which is a constraint rather than a selection rule.

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