Server exposes 4 Ethereum RPC tools with basic schemas and descriptions. All tools have input schemas with type definitions and parameter descriptions, meeting minimum requirements. However, descriptions are generic and lack LLM-optimized guidance on WHEN to use each tool vs alternatives. No output schemas documented. Error handling returns raw JSON-RPC errors without recovery guidance. Tool naming follows RPC conventions (eth_*) rather than action-verb patterns (get_*, execute_*), reducing clarity for LLM tool selection. The execute_eth_rpc catch-all tool violates single-responsibility principle by accepting arbitrary methods.

• Rename tools to action-verb pattern: eth_blockNumber → get_latest_block_number, eth_getBalance → get_eth_balance, eth_call → execute_contract_call. This makes intent obvious to LLMs without reading descriptions.
• Expand descriptions to 50-200 chars with WHEN guidance: 'Get the latest mined block number. Use this to check chain progress or as a reference point for block-relative queries. Returns a hex-encoded integer.' Include the typo fix ('latest' not 'lastest').
• Remove execute_eth_rpc or restrict it to advanced RPC methods not covered by specific tools (e.g., eth_getLogs, eth_getTransactionReceipt). Document which methods should use execute_eth_rpc vs dedicated tools.
• Add outputSchema to each tool definition documenting return structure. E.g., eth_getBalance returns {hex: string, wei: string, eth: number}. This enables LLMs to plan downstream operations.
• Enhance error messages with recovery hints. Catch common failures (invalid address format, network errors, contract reverts) and return actionable guidance: 'Invalid address format: expected 0x-prefixed 40-char hex string. Example: 0x742d35Cc6634C0532925a3b844Bc9e7595f42bE'