This server has solid tool naming conventions and good parameter schemas with proper constraints (enums, min/max bounds). Descriptions are present and moderately detailed for most tools. However, output schemas are completely undocumented, the tool definitions do not specify what fields are returned, preventing LLMs from planning downstream operations. Error handling guidance is absent. Parameter descriptions vary in quality, and some critical context is missing (e.g., what fields does get_contact return? what does search_contacts return beyond matches?). The server sits in the 'fair to good' range but falls short of production-grade due to missing output documentation and error recovery guidance.

• Document output schemas for all tools. For list_contacts, specify: 'Returns {contacts: [{resourceName, displayName, emailAddresses[], phoneNumbers[], organizations[], ...}], nextPageToken?: string, totalSize?: number}'. This enables the LLM to understand what data is available and how to chain calls.
• Add error handling examples in descriptions. E.g., 'If resourceName is invalid or contact is deleted, returns error: Contact not found. Try search_contacts(displayName) to find the correct resourceName.'
• Clarify chaining IDs in list_contacts and search_contacts: 'Results include resourceName, which is required by get_contact() to retrieve full details.'
• Expand readMask description with examples and a link to valid field names. E.g., 'readMask: comma-separated fields like names, emailAddresses, phoneNumbers, organizations. Omit to return all fields. See https://developers.google.com/people/api/rest/v1/people/get#personfieldmask'.
• Add context for when to use each tool. E.g., 'Use list_contacts to browse paginated contact list. Use search_contacts for keyword matching. Use get_contact for detailed info on a known contact. Use search_directory (Workspace only) for organizational lookups.'
• Specify pagination behavior: does nextPageToken indicate more results? Is totalSize available? How many results are returned per page by default?
• Add examples of valid query syntax for search_contacts and search_directory in descriptions or as enum hints.

Inferred effective spec: 2026-07-28+.

• Relies on Dynamic Client Registration (deprecated) - use Client ID Metadata Documents (CIMD)