Server has 6 tools with basic schemas and descriptions, but significant quality gaps. All tools have descriptions (10-100 chars, mostly adequate), and input schemas are present with Zod validation. However, parameter descriptions are sparse or missing entirely. Most tools lack output schema documentation. Error handling is minimal, generic catch blocks return only error messages without recovery guidance. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite all tools being READ_ONLY. Parameter constraints are underspecified (e.g., queryPnls accepts arbitrary sort/projection objects without validation). No pagination guidance for list-like tools (queryPnls, getTopTokens, getLeaderboard). Tool composition is reasonable but lacks chaining metadata (e.g., getTokenDetailsFromMints should return mint alongside name/symbol for downstream use).

• Document output schemas for all tools. Specify the structure of returned data (e.g., parseTransactions returns [{signature, status, timestamp, ...}], queryPnls returns [{wallet, token, pnl, usd, ...}]). Include field types and descriptions.
• Add detailed parameter descriptions for queryPnls. Document what keys are valid in 'filter' (e.g., 'wallet: string (Solana address)', 'token: string (mint or symbol)'), 'sort' (e.g., '{pnl: 1 or -1, usd: 1 or -1}'), and 'projection' (e.g., '{wallet: 1, pnl: 1}').
• Add tool annotations. Declare readOnlyHint: true for all 6 tools so LLMs know they are safe to retry and have no side effects.
• Improve error messages with recovery guidance. Instead of 'Error: 404', return 'Wallet not found. Verify the address is a valid Solana wallet (44-44 base58 chars). Try search_wallets() if you only have a name.'
• Add pagination guidance. For queryPnls, getTopTokens, getLeaderboard, document the limit parameter range (1-1000) and advise LLMs to use limit=20 by default. Specify if results are sorted by relevance or if a next_cursor is available.