Two tools with minimal documentation. whisper-message has a basic schema (message: string, minLength=1) and a description that includes example JSON, but lacks parameter-level description detail and output schema documentation. fetch-and-whisper-quote has an empty input schema (no parameters) and a vague description that doesn't explain what it returns or when to use it. Neither tool declares error handling, recovery guidance, or idempotency. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite both being WRITE operations. Descriptions are under 200 chars but lack LLM-optimized structure (WHAT, WHEN, RETURN). Output schemas are completely undocumented.

• Add explicit output schema to whisper-message: { txHash: string, explorerUrl: string, chainFrom: string, chainTo: string }. Document in tool description.
• Define fetch-and-whisper-quote input schema with at least one parameter (e.g., quoteType?: enum or resourceId: string). Currently empty schema makes tool non-functional.
• Add tool annotations: both tools should declare destructiveHint=true (irreversible cross-chain sends) and idempotentHint=false (retries risk duplicate messages).
• Enhance error messages with recovery guidance: 'Invalid message (empty). Provide a non-empty string.' or 'API error: check CHANNEL_API_KEY and BASE_URL environment variables.'
• Expand descriptions to 100-200 chars following WHAT-WHEN-RETURN pattern: 'Send a cross-chain message via Whisper (Base→Ethereum). Use when you need to relay data across chains. Returns LayerZero explorer URL and transaction hash.'