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

With no annotations provided, the description carries the full burden, and it delivers extensively: JavaScript execution, same-host restriction, robots.txt compliance with skipped pages named, free/paid gating, the exact $1.00 price and payment rails, the 402 flow, and the poor-yield failure mode that explicitly does not bill. This is far richer behavioral disclosure than annotations would typically supply.

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 description is long but well-structured: core capability first, then explicit FREE/PAID sections, then failure mode. Nearly every sentence carries operational information an agent needs. Minor deductions for the promotional clause 'Priced at a dollar because it is up to 25 real browser renders, not a lookup' and slight redundancy between the schema and prose on the payment flow.

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?

This is a complex tool - payment rails, free/paid modes, crawl constraints, robots.txt, and a custom failure path - and with no output schema, the description must explain return values, which it does: the crawl plan for free calls, rendered clean text for paid calls, and the named-page poor-yield error. Nothing an agent needs to call it correctly and set expectations 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 the baseline is 3, but the description adds genuine meaning beyond the schema: it explains the `full` flag's 402/price flow, elaborates that `payment` is a previously signed x402 payload to resubmit, and frames `pages` within the 25-page hard cap and per-render cost rationale. The schema says 'sign it and call again' but the description clarifies the failure and non-billing semantics around it.

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?

The description opens with a specific verb and resource: 'Render a whole section of a site - up to 25 pages - in one call and get every page back as clean text, with JavaScript executed.' The multi-page crawl scope clearly separates it from the sibling page_extract (single-page) tool, and the 'whole section of a site' phrasing makes the tool's distinguishing purpose obvious without needing to inspect 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?

The description gives strong decision context: when to use the FREE crawl plan vs the PAID render, the full payment flow (402 with rails, sign, resubmit with `payment`), the same-host constraint, and the poor-yield failure behavior with no billing. It does not explicitly name an alternative for single-page extraction or state a when-not condition, so it falls just short of the explicit-exclusion bar.

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