x402_scrape_url

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

With no annotations provided, the description carries full disclosure burden and succeeds admirably. It reveals pricing model, authentication requirements, timeout limits, underlying technology (Playwright), return value structure, and available modes (paid vs. free test fixture data). No contradictions exist.

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 efficiently structured with zero waste: purpose statement, pricing/auth constraints, technical capabilities (Playwright/SPA), operational limits (timeout), and return format. Every sentence conveys essential information required for tool invocation decisions.

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?

Despite lacking an output schema, the description comprehensively documents return values (markdown, links, tables, images, metadata, status). For a complex paid API with authentication requirements, the description provides sufficient context for correct agent operation without external documentation.

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%, establishing a baseline of 3. The description adds significant value by contextualizing the wait_for parameter for 'async SPA content' and explaining the auth constraint (X402_PRIVATE_KEY) that gates functionality. This goes beyond the raw schema definitions.

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 ('Scrape') and resource ('web page'), clearly defining the scope as single-page extraction. It distinguishes itself from sibling x402_crawl_site by emphasizing structured data extraction (markdown, links, tables) versus presumably broader crawling functionality.

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 provides clear prerequisites (X402_PRIVATE_KEY required for paid mode), constraints (8-second hard timeout), and cost information ($0.02 USDC). It specifies when to use the optional wait_for parameter ('for async SPA content'). However, it does not explicitly contrast with x402_crawl_site for multi-page scenarios.

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