Server has 6 tools with complete input schemas and descriptions. Naming follows verb_noun pattern (ask_claude, summarize, code_review, translate, sentiment, crypto_analysis). Descriptions are present and moderately detailed (100-200 chars), meeting baseline minimums. However, parameter descriptions lack depth on constraints and error recovery. Output schemas are not formally documented, responses are inferred from code. Error handling exists but lacks actionable recovery guidance per pattern:recovery-guide. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite all tools being READ_ONLY. Pricing information is embedded in descriptions rather than structured metadata.

• Add explicit output schema documentation for each tool. Define return object structure with typed fields (e.g., 'Returns {answer: string, usage: {input_tokens: number, output_tokens: number}, cost_usdc: string}').
• Implement tool annotations in Zod schemas: add .describe() with readOnlyHint metadata or use a custom annotation layer to mark all tools as read-only per spec 2026-07-28.
• Enhance error messages with actionable recovery steps. For 402 errors: 'Payment required. Set up x402 wallet: (1) Install Base network wallet, (2) Fund with USDC, (3) Retry.' For API errors: 'Service unavailable. Retry in 30s or check status at [URL].'
• Document parameter constraints in descriptions. E.g., translate: 'target_language: ISO 639-1 code (e.g., es, fr, ja) or full name (Spanish, French, Japanese)'. crypto_analysis: 'tokens: array of 1-10 uppercase symbols (e.g., ["BTC", "ETH"])'.
• Add a separate cost_estimate tool or metadata field to help agents track cumulative expenses before executing expensive operations. Return cost breakdown in all tool responses.