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

Annotations already cover the safety profile (readOnlyHint, openWorldHint, destructiveHint=false), so the description's added value is the cost and payment model: $0.009 USDC per call via x402 on named chains, automatic payment for x402 MCP clients, and a free-sample path. It discloses the cost/speed penalty relative to web_scrape, which is genuinely useful behavioral context beyond annotations, though it says nothing about timeouts or failure modes on JS-heavy pages.

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?

Front-loads purpose and the routing decision, then tacks on params, price, and a sample. Every sentence carries information, but the payment-chain enumeration and sample JSON make the block denser than strictly needed.

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?

No output schema exists, and the description compensates by naming the returned fields (title, description, word_count, links). Combined with the payment disclosure and when-to-use guidance, an agent has enough to invoke it correctly, though truncation/pagination edge behavior is left to the schema's max_chars note.

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 description coverage is 100%, so all three parameters (url, max_chars, include_links) are already documented with types and defaults. The description restates them with defaults but adds no syntax or format detail beyond the schema — baseline 3 is appropriate.

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 (read/render) and resource (ONE JavaScript-heavy page) plus the mechanism (real Chromium browser) and the return payload (rendered text, title, description, word_count, optional links). It is clearly distinguishable from siblings like web_scrape and page_extract without opening either schema.

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 an explicit when-to-use condition — 'use it only when web-scrape returns little or no content' — and names the alternative along with the trade-off (slower and pricier). Routing is unambiguous.

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