Email MCP has 3 tools with basic definitions but significant quality gaps. All tools have descriptions (10-50 chars, below the 50-200 char baseline for LLM optimization) and visible input schemas with types. However, parameter descriptions are minimal or missing context. No output schemas documented. Error handling returns generic strings without recovery guidance. Tools lack idempotency hints and confirmation patterns for destructive operations (send_email). No tool annotations present. Naming is clear (verb_noun pattern) but descriptions don't explain WHEN to use each tool or dependencies between them.

• Expand tool descriptions to 50-200 chars. Example: 'get_recent_emails: Retrieve the N most recent emails from a specified folder (INBOX, Sent, Drafts, etc.). Returns email metadata (from, subject, date) and body text. Use this to browse recent messages; use search_emails to find specific emails by keyword.'
• Document output schemas explicitly. Define that get_recent_emails returns a list of objects with fields: {from: string, subject: string, date: string, body: string}. Declare return type in docstring.
• Add tool annotations: mark send_email_message with destructiveHint=true; mark get_recent_emails and search_emails with readOnlyHint=true. Use FastMCP's @mcp.tool(annotations={...}) if supported.
• Implement confirmation pattern for send_email_message. Return a dry-run response showing recipient, subject, body, and ask for explicit confirmation before sending. Or add a 'dry_run' boolean parameter (default=false).
• Improve error messages with recovery guidance. Example: 'Failed to connect to email server. Check that EMAIL_USER and EMAIL_PASSWORD environment variables are set and credentials are correct. Retry after fixing credentials.' Categorize errors as retryable vs. user-fixable.