Chronos MCP has basic tool definitions with schemas and descriptions present, but falls short of production quality. All 4 tools have input schemas and descriptions, but descriptions are minimal (10-50 chars, well below the 194-char baseline). Critical security issue: connect_wallet and transfer_funds expose secret keys as parameters, violating secret-injection pattern. Parameter descriptions lack format/constraint details. No output schemas documented. Error handling is minimal, McpError responses lack recovery guidance. Tool composition is reasonable (separate read/write operations), but descriptions don't explain when to use each tool or what they return.

• Move secret key handling to server-side environment variables (STELLAR_SECRET_KEY already loaded via dotenv). Remove secretKey parameter from connect_wallet and transfer_funds. Accept only publicKey for read operations; for transfers, use the pre-configured secret key or implement a secure key management pattern.
• Expand tool descriptions to 100-200 chars. Example: 'connect_wallet' → 'Authenticate to a Stellar wallet using a secret key. Returns the wallet public key and account details. Call this first to verify wallet access before listing tokens or transferring funds.'
• Document output schemas in tool descriptions or as a separate schema field. Example: 'Returns {publicKey: string, accountExists: boolean, balances: [{asset: string, balance: string}]}'.
• Add format/constraint details to parameter descriptions. Example: 'amount' → 'Amount to transfer as a decimal string (e.g., "100.50"). Must be positive and not exceed wallet balance.'
• Enhance error responses with recovery guidance. Example: Instead of 'Secret key is required', return 'Secret key not configured. Set STELLAR_SECRET_KEY environment variable or call connect_wallet with a valid secret key first.'