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

Annotations already cover read-only and open-world safety, but the description adds substantial context beyond them: the render:true behavior (real browser, slower, returns plain text), the pricing model ($0.0025 USDC per call paid in-call via x402 across named chains), auto-payment for x402 clients, and a free example invocation. This is well past the annotation bar.

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-loaded with purpose, then routing, then params, then pricing. Dense but every clause carries useful information; the only mild redundancy is restating schema-documented param defaults. Structured as a single block rather than cleanly separated lines.

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, the description still describes the return shape (title, meta description, main content with headings, lists and links) plus link behavior. Combined with routing, cost, and render fallback guidance, an agent has everything needed to call it 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 schema already documents all four parameters. The description largely restates them (url required, max_chars default 8000/max 60000) and only marginally adds the 'slower' nuance for render. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('URL to Markdown web scraper: read any web page as clean, LLM-ready Markdown') and immediately scopes it ('Default tool for reading ONE web page whose URL you have'). It distinguishes itself from siblings by naming the exact tool to use for other shapes of the task.

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?

Explicit routing rules: 2-5 URLs → web-read-batch, whole site → site-crawl, question but no URL → search-read, JS app returning empty → render:true or webpage-reader. When-to-use and named alternatives are both present.

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