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

Annotations only cover read-only and open-world; the description adds substantial context beyond that: no JS rendering with the consequence that browser-built pages return short, link counts included, per-call price of $0.002 with x402 payment on three chains, and that failed calls are free. These are exactly the behavioral facts an agent needs before paying for a call.

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 tight sentences with no filler, front-loaded with what is returned and then immediately bounded by scope and rendering limits before the cost note. Every clause carries decision-relevant information.

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?

An output schema exists, yet the description still summarizes the return shape and adds the limitations and pricing an agent must weigh. For a two-parameter read tool, nothing needed to invoke 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 coverage is 100%, so both url and maxChars are already documented in the schema, and the description adds no syntax or format detail about them. Baseline 3 applies since the schema does the work here.

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 ('Reads one public web page') and enumerates the return payload (title, description, main text as Markdown, link counts). The scoping clause 'Reads only the page you name: no crawling of other pages' clearly separates it from crawler/site-wide siblings.

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 clear usage context and implicit exclusions ('no crawling of other pages, no JavaScript rendering'), telling the agent when this tool will underperform. It does not name a specific sibling alternative for the crawl-everything or JS-rendered case, so it falls short of the explicit-alternative bar.

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