Server has 6 tools with complete input schemas and descriptions. Naming follows verb_noun pattern (sol_balance, sol_transfer, sol_swap). Descriptions are present (avg ~80 chars) but lack depth on when/why to use each tool and error recovery guidance. Parameters are typed and described, but lack constraints (enums, ranges, patterns). No output schemas documented. Error handling is minimal, no recovery guidance or categorization. Security: private key injection via env var is correct, but no audit logging visible. Composition is reasonable (separate read/write tools), but no pagination support for list-like operations.

• Document output schemas for all tools. E.g., sol_balance should return {balance_sol: number, tokens: [{mint: string, symbol: string, amount: number, usd_value: number}]}. sol_transfer should return {tx_hash: string, status: string, timestamp: string}.
• Add numeric constraints: slippage 0.01 - 50 (percent), amount > 0, max_tx_sol from config. Use JSON Schema minimum/maximum and pattern fields.
• Expand tool descriptions to 100 - 150 chars explaining when to use each. E.g., 'Get SOL and token balances for a wallet. Use this for quick balance checks; use sol_portfolio for USD-valued holdings overview.'
• Implement error recovery guidance in tool descriptions and error responses. E.g., 'If transfer fails with insufficient balance, call sol_balance first to check available SOL.'
• Add dry-run or confirmation step for irreversible operations. E.g., sol_swap could accept a 'dry_run: bool' parameter that returns estimated output without executing, or return a confirmation_required response requiring user approval.