Gmail MCP server has 17 tools with significant definition gaps. Tool names follow verb_noun convention (get_, create_, send_, list_) which is good. However, source code inspection reveals NO visible input schemas, parameter descriptions, or output documentation in the provided files. The index.ts is minimal (2 lines), and while tool files are listed, their actual definitions are not shown. Without seeing the actual tool class implementations, parameter schemas, and descriptions, scoring must be conservative. The bundle file shows tool imports but not their definitions.

• Provide complete tool source files showing actual class definitions, input schemas, parameter types, and descriptions. Current dump only shows imports and file references.
• Add 50-200 character descriptions to every tool explaining WHAT it does, WHEN to use it, and any prerequisites. Example: 'send_email: Compose and send an email message. Use this after create_draft to send a prepared message. Returns message ID and timestamp.'
• Define JSON Schema input parameters for all tools with type, description, enum (for constrained values), and minLength/maxLength/pattern for strings. Example: { 'to': { 'type': 'string', 'description': 'Recipient email address', 'pattern': '^[^@]+@[^@]+\.[^@]+$' } }
• Document output schemas showing what fields each tool returns. Example: send_email returns { 'message_id': string, 'thread_id': string, 'timestamp': string (ISO 8601), 'labels': string[] }.
• Add error handling that returns actionable guidance. Instead of 'Error: 404', return 'Message not found. Try search_messages() with keywords first, or list_messages() to browse recent emails.'