Server defines 6 tools with explicit schemas and descriptions visible in server.js. However, critical gaps undermine quality: (1) Naming lacks consistency, 'multipu_get_live_memes' uses 'memes' (colloquial) instead of 'tokens'; (2) Descriptions are present but generic, averaging ~120 chars, lacking WHEN/WHY guidance for LLM selection; (3) Parameter descriptions are minimal, 'amount' lacks units, range, or precision; (4) No output schemas documented, LLMs cannot predict response structure; (5) Error handling absent, no recovery guidance or categorization; (6) Irreversible tool (multipu_swap_tokens) has no dry-run, confirmation, or rollback pattern. Schemas are well-formed JSON Schema with types and enums, but lack depth. No tool annotations (readOnlyHint/destructiveHint) despite clear risk levels.

• Document output schemas for all 6 tools. Include field names, types, and sample structure. Example: multipu_get_live_memes should return {tokens: [{id, name, symbol, chain, price, volume}], total, page, hasMore}.
• Add dry-run and confirmation pattern to multipu_swap_tokens. Implement keeperhub_dry_run_swap as a prerequisite step, then require explicit confirmation before executing real swap. Return transaction hash and estimated impact in response.
• Enhance parameter descriptions with constraints: 'amount' → 'Amount in base currency (SOL/BNB/ETH), min 0.001, max 1000000'; 'page' → 'Page number (1-based, default 1)'; 'query' → 'Optional token name/symbol filter; if omitted, returns all active launches sorted by volume.'
• Add error handling guidance to tool descriptions. Example: 'If API returns 429 (rate limit), retry after 60s. If 404 (token not found), call multipu_get_live_memes to discover available tokens. If 403 (insufficient balance), check multipu_get_wallet_balances first.'
• Rename 'multipu_get_live_memes' to 'multipu_get_live_tokens' for clarity and consistency with domain terminology. Update description to emphasize token discovery and filtering by chain/status.