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

Annotations only declare readOnly/openWorld/destructive hints. The description adds substantial non-obvious behavior: per-call pricing ($0.05 USDC), x402 in-call payment across four chains, partial-failure semantics ('A failed page is reported with its error while the others still return'), billing conditional on at least one page read, parallel fetching, and URL dedup. This is exactly the context annotations cannot carry.

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 the core capability and scoping, then pricing/alternatives/sample. It is long, but each block (when-to-use, failure behavior, alternatives, price, free sample) carries distinct decision-relevant information rather than filler. The embedded sample input is borderline verbose but operationally useful for a paid tool.

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 describing the return shape (Markdown per page with title and meta description, optional links), failure reporting, and billing outcome. Combined with the named alternatives, an agent has everything needed to invoke and interpret results 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 description coverage is 100%, so the schema already documents all three parameters including ranges and defaults. The description largely restates them ('urls (1 to 20, required), max_chars per page (500 to 30000, default 8000), include_links') without adding format or edge-case detail. 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+resource+scope ('Bulk web scraper: read up to 20 web pages... each as clean, LLM-ready Markdown with title and meta description'). It explicitly distinguishes itself from siblings web-scrape (single URL) and site-map (find URLs), so an agent can route without opening schemas.

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 ('Use when your agent works through a list of URLs (search results, product pages, a sitemap, a link list)') plus named alternatives with conditions ('For a single URL use web-scrape, to find the URLs of one site first use site-map'). Nothing is left to inference.

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