Six tools with clear verb-noun naming and solid descriptions (avg 120 chars). All tools have input schemas with typed properties. Strengths: dry-run pattern for writes, explicit confirmation checks, good parameter descriptions (E.164 format, ISO 8601, IANA timezone). Weaknesses: no output schemas documented, missing descriptions on some parameters (list_calendars has empty properties), no error recovery guidance, no pagination support despite potential for large result sets.

• Document output schemas for all six tools. Example for search_contacts: 'Returns {contacts: [{id, firstName, lastName, email, phone, tags}], total}'. This enables LLMs to chain tools correctly.
• Add explicit result limits to descriptions. E.g., 'search_contacts returns up to 20 results (configurable via limit param, max 100). Use pagination for larger datasets.'
• Enhance error messages with recovery paths. Wrap ghlRequest errors with context: 'Contact not found. Try search_contacts(query=name) to find the correct ID.'
• Document list_calendars parameters explicitly, even if empty in the UI. Add note: 'No parameters required, uses locationId from environment. Returns all calendars in the location.'
• Add tool annotations (readOnlyHint, destructiveHint) to schema. Mark search_contacts, get_contact, list_calendars, get_free_slots as readOnly=true; mark create_contact, book_appointment as destructive=true (when confirm=true).