Server has 4 tools with significant quality gaps. Tool names lack clear action verbs (googleAuthLogin is acceptable, but addCalendarEvent and listCalendarEvents are generic). Descriptions are present but minimal (10-50 chars, below the 50-200 char LLM-optimized baseline). Input schemas exist but lack proper type definitions and descriptions for most parameters. No output schemas documented. Error handling is minimal. The server uses STDIO transport, which is not remotely accessible.

• Expand all tool descriptions to 50-200 characters. Example: 'addCalendarEvent' → 'Create a new event in Google Calendar. Requires authentication via googleAuthLogin. Returns event ID and calendar link. Specify start time in YYYY-MM-DD HH:mm format and duration in minutes.'
• Add output schemas to all tools. Document what fields are returned (e.g., addCalendarEvent returns {id: string, htmlLink: string, startTime: string, endTime: string}).
• Add parameter descriptions in English with format/constraint details. E.g., startTime: 'Event start time in YYYY-MM-DD HH:mm format (24-hour, Asia/Seoul timezone). Example: 2024-01-15 14:30'.
• Implement error handling that returns actionable messages. E.g., 'Authentication failed: token expired. Call googleAuthLogin to re-authenticate.' instead of raw error codes.
• Add tool annotations (readOnlyHint, destructiveHint) to clarify side effects. Mark addCalendarEvent as destructiveHint=false (it creates, not deletes), and listCalendarEvents as readOnlyHint=true.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry