The server exposes 11 tools with mixed quality. Most tools have adequate descriptions (150-350 chars), but parameter schemas vary significantly. 9 of 11 tools have reasonable input schemas with type definitions, but descriptions are inconsistent across parameters. The 'chat' tool has a well-structured schema with proper type annotations and descriptions. However, several tools (liquidity_pulls, whale_swaps) have empty input schemas {}, which violates the parameter documentation requirement. Tool naming follows verb_noun convention reasonably well (list_models, web_extract, token_safety), but descriptions sometimes conflate multiple concerns (e.g., seo_audit mixes SEO and GEO scoring in a single tool description without clarity on when each is needed). Output schemas are NOT documented anywhere in the source code, we cannot see what fields these tools return, which is a critical gap for composition and agent planning. Error handling descriptions are minimal; tools mention 'PAID x402 service' but do not explain what happens on payment failure, wallet insufficiency, or network errors. The tool descriptions are optimized for human reading but lack LLM-specific guidance on when to select a tool over similar ones.

• Add explicit output schemas for all 11 tools. For each tool, document the response object structure (field names, types, optionality, nesting). Example for list_models: 'Returns an array of model objects, each with: {id: string, provider: string, input_price_per_1k_tokens: number, output_price_per_1k_tokens: number}'.
• For liquidity_pulls and whale_swaps, define input schemas with at least one filtering parameter (e.g., 'since_block', 'limit', 'pool_address') to replace the empty {} schema. If these tools truly take no parameters, document that they return the N most recent events in real-time order.
• Rewrite error handling descriptions for all PAID tools. Template: '[Tool name] may fail if: wallet is unfunded (ask user to fund wallet on Base), network error (retryable), or invalid input (fix parameters). On 402 Payment Required, the tool returns the payment requirements, sign and retry via WALLET_PRIVATE_KEY.'
• For seo_audit, split the description or add parameter-level guidance: 'Set mode=seo for SEO compliance only (meta, headings, structure). Set mode=geo for generative-engine-optimization (content quality, AI index eligibility). Use mode=both (default) for full audit. SEO is faster; GEO requires content analysis.'
• Add constraint details to parameter descriptions. Examples: token_safety token param: 'ERC-20 contract address on Base (0x followed by 40 hex chars, case-insensitive)'. new_pairs limit param: 'Maximum number of pairs to return; 1 - 200, default 50. Note: if fewer than limit pairs exist, all are returned.'