Three tools with solid descriptions (150-200 chars each) and clear use cases. All tools have input schemas with type definitions and parameter descriptions. However, output schemas are not formally documented in the tool registration, only mentioned in code comments. Tool names follow verb_noun pattern (html_to_markdown, extract_page, service_info). Parameters are well-described with enums for 'mode'. Missing: explicit output schema documentation, error recovery guidance in descriptions, and per-parameter validation rules.

• Add explicit output schema documentation to tool registration. Use a 'returns' field or extend the description to include: 'Returns: {markdown: string, url: string|null, rendered: boolean, ms: number, ...}' so LLMs know what fields to expect.
• Enhance error descriptions with recovery paths. E.g., 'If the page fetch fails, verify the URL is publicly accessible and not behind authentication. If render=true times out, try render=false for static pages.'
• Document x402 payment flow in tool descriptions. Add: 'Paid tool via x402 (USDC on Base). Unpaid calls return -32402 payment-required error; x402-aware clients sign and retry with payment authorization.'
• Expand service_info description and output schema. Clarify: 'Returns pricing, payment methods, and service status. Call this to check current rates and available payment networks before invoking paid tools.'
• Add parameter constraints for 'render'. Specify: 'render=true adds ~2-5s latency and increases cost. Use only for JS-rendered SPAs (React/Next/Vue); static HTML pages do not need rendering.'

Inferred effective spec: 2026-07-28+.

• Relies on Stateful initialize / Mcp-Session-Id (removed; protocol is stateless) - make each request self-contained