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

With no annotations, the description carries the burden and does reasonably well: it discloses the headless-browser mechanism, that it waits for network settle, the Markdown return format, and the 0.01 USDC x402 cost per call. It omits timeout behavior, failure modes on bot-protected pages, and what happens when content exceeds maxChars.

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?

Three short sentences: mechanism and return format first, then the selection heuristic, then the cost note. Nothing is padded and the most important information is front-loaded.

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, but the description states the return type (Markdown) and the description plus schema together cover all three parameters including the two-step payment handshake. Minor gaps remain around timeouts, size limits, and failure behavior for blocked or JS-erroring pages.

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 67%; url and paymentProof are well described in the schema itself. The description adds payment/cost context but says nothing about maxChars truncation semantics, which is the one parameter with no schema description at all. Baseline 3 is appropriate given the schema does most of the work.

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 and mechanism: loads a URL in real headless Chromium via Cloudflare Browser Rendering and returns Markdown. It also distinguishes itself from the extraction path by explaining plain extraction can return an empty shell, so an agent can tell it apart from siblings like web_extract or web_screenshot.

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?

"Use for single-page apps where plain extraction returns an empty shell" gives a concrete selection condition. It stops short of naming web_extract explicitly or stating when not to use this (e.g. static pages, where the cheaper sibling suffices), so it's clear context without full routing.

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