Two read-only tools with basic schemas and minimal descriptions. Both tools have proper JSON Schema with types and required fields, but descriptions are generic (under 100 chars) and lack context about when to use each tool or what they return. Parameters have descriptions but lack format constraints (ISO 8601 dates should specify format). No output schema documented. No error handling guidance. No parameter validation rules stated. Naming is clear (list_events, get_event) but descriptions don't explain the distinction or use cases.

• Add 'format': 'date-time' to start and end parameters in list_events schema to enforce ISO 8601 validation at the schema level.
• Expand tool descriptions to 100-200 chars explaining use cases: 'List calendar events within a date range. Use this to find all events in a time window. For details on a specific event, use get_event. Returns event summaries with start/end times and attendees.'
• Document output schema for both tools. Specify that list_events returns an array of event objects with fields: id, summary, start, end, attendees. get_event returns a single event object with full details.
• Add pagination to list_events: accept 'limit' (1-250, default 50) and 'page_token' parameters. Return results with a 'next_page_token' field for continuation.
• Add error handling guidance in descriptions: 'If calendar_id is invalid, the tool will return an error. Verify the calendar exists or use "primary" for the default calendar.'