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

Annotations cover only readOnly/openWorld/idempotent, and the description goes well beyond that: exact price, that failures and the 402 are not charged, that payment is forwarded as a header not body data, and a prompt-injection warning about treating page text as data. This is unusually rich behavioral disclosure for a paid read tool.

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?

The paragraph is long and em-dash heavy, but it is front-loaded with the price and core purpose and every clause carries operational information (redirects, error codes, billing). No filler sentences, though it could be split for scanability.

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, so return values need no prose. The description still covers pricing, payment handshake, error semantics, size limits, and safety guidance — everything an agent needs to call a paid, open-world read tool correctly.

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 the baseline is 3, but the description adds real value: it restates the maxChars cap/default in context ('up to 100,000 characters (default 40,000)') and, critically, explains the two-call payment choreography around the `payment` parameter that the schema alone only hints at.

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 (any public web page) and enumerates exactly what the caller receives: title, meta description, canonical URL, stripped body, first 50 links, word count. No sibling tool in the list does web-page reading, so the scope is unambiguous.

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 operating context: one page per call, redirects not followed (call again with the named target), JS-rendered pages return 422, non-2xx/timeout/binary return >= 400, and the first call returns a 402 challenge to be answered on a second call. It does not name an alternative tool, but no plausible alternative exists in the sibling set.

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