PAID (x402): returns x402 payment instructions for a PDF render of a publicly reachable URL, via a real, robots-respecting headless browser. Currently soft-skips 503 until Cloudflare Browser Rendering is provisioned.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | absolute http(s) URL to render to PDF |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It discloses using a 'robots-respecting headless browser' and a 'soft-skip 503' behavior, but lacks details on return format, error handling, or payment flow. The behavioral traits are partially covered.
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?
Two sentences, front-loaded with the essential action, no redundant information. Every sentence adds value, from payment hint to current limitation.
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?
The description covers the paid nature, browser type, and a special behavior (503 skip), but does not explain what 'x402 payment instructions' are or how to handle them. Lacking output schema, the agent is left without return value info.
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% for the url parameter. The description does not add meaning beyond the schema's 'absolute http(s) URL to render to PDF'. Baseline score applies.
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 clearly states it returns x402 payment instructions for a PDF render via a headless browser. It distinguishes from sibling tools like render_screenshot by specifying 'PDF render' and 'payment instructions', though the exact output (payment instructions vs. PDF) may cause confusion.
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 implies usage when a paid PDF render is needed ('PAID (x402)'), but does not explicitly state when to use versus alternatives like read_url or render_preview. No exclusions or prerequisites are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Tools have distinct purposes (read full, read preview, render PDF, render preview, render screenshot). However, render_preview is a discovery stub for both PDF and screenshot, which could cause some ambiguity about which specific render tool it relates to.
Consistent verb_noun pattern with underscores: read_url, read_url_preview, render_pdf, render_preview, render_screenshot. Naming clearly indicates whether the tool reads text or renders visual output.
Five tools is appropriate for a web page reader that offers both text extraction and rendering capabilities. The set is neither too sparse nor overloaded.
The core read tools cover the primary purpose of fetching and converting URLs to markdown. The rendering tools are included but currently non-functional (return 503 or x402), leaving a gap in visual rendering capabilities. JavaScript-rendered pages are also unsupported.