Server has 5 tools with basic schemas and descriptions, but significant gaps in parameter documentation and output structure. Tool names follow verb_noun convention (list_*, read_*, search_*, send_*), which is good. However, parameter descriptions are minimal or missing entirely. For example, 'folder' and 'limit' parameters lack descriptions in the schema definitions visible in code. Descriptions are present but brief (10-30 chars for most tools), below the 50-200 char baseline for LLM-optimized descriptions. No output schemas documented. Error handling returns plain text without recovery guidance. The 'send_email' tool lacks confirmation/dry-run pattern for an irreversible operation.

• Add full parameter descriptions to all inputSchemas. For 'folder', add: 'IMAP mailbox folder name (default: INBOX). Call list_folders() to see available folders.' For 'limit', add: 'Maximum number of results to return (1-100, default: 10).'
• Expand tool descriptions to 80-150 chars. Example: 'list_recent_emails: Retrieve the N most recent emails from a mailbox folder. Use this to browse inbox or search results. Returns uid, sender, subject, date, and read status for each email.'
• Document output schemas for each tool. Example for list_recent_emails: 'Returns array of {uid: number, from: string, subject: string, date: string, seen: boolean}.'
• Add confirmation pattern to send_email. Implement a 'dry_run' boolean parameter (default false) that returns a preview without sending. Or require explicit 'confirm: true' parameter.
• Enhance error messages with recovery guidance. Example: 'Email uid=123 not found in INBOX. Try list_recent_emails() to see available emails, or search_emails() to find by subject/sender.'