Google Calendar MCP has well-structured schemas with proper Zod definitions and JSON Schema conversion. All 7 tools have descriptions and input schemas. However, descriptions are generic (avg ~50 chars, below the 194-char baseline), parameter descriptions lack actionable constraints, and output schemas are not documented. Error handling is minimal, no recovery guidance or categorization. Tool composition is sound (each does one thing), but missing pagination for list_events and search_events, and no confirmation pattern for destructive delete_event.

• Document output schemas for all tools. E.g., create_event returns {eventId: string, summary: string, start: ISO8601, end: ISO8601, ...}. This enables LLMs to chain calls (create_event → update_event with returned eventId).
• Expand tool descriptions to 100 - 200 chars. Include WHEN to use, prerequisites, and side effects. E.g., delete_event: 'Permanently deletes a calendar event. This action is irreversible. Use with caution, consider archiving instead if available.'
• Add pagination to list_events and search_events: accept maxResults (default 10, max 100) and nextPageToken. Return total count and nextPageToken in response so agents can iterate large result sets.
• Implement confirmation pattern for delete_event: add a dry_run parameter (default false) or require explicit confirmation. Return {confirmed: false, message: 'Ready to delete event X. Call again with confirmed=true to proceed.'}
• Add error handling with recovery guidance. E.g., if eventId not found, return 'Event not found. Try search_events(query=...) to find the event ID first.' Categorize errors: retryable (timeout, rate limit), user-fixable (invalid input), fatal (permission denied).