Four tools with basic schemas and descriptions, but significant gaps in parameter documentation and error handling. Tool names follow verb_noun convention (schedule_meeting, get_free_slots, get_booked_slots, get_knowledge). Descriptions exist but are brief (34-72 chars, below the 194-char baseline). Input schemas present with type declarations, but parameter descriptions are minimal or missing context. No output schemas documented. No error handling guidance. No tool annotations (readOnlyHint/destructiveHint). Missing idempotency and recovery patterns.

• Document output schemas for all tools. Example: schedule_meeting returns {meeting_id: string, status: string, start_time: string, end_time: string, booked: boolean}. This enables chaining and field extraction.
• Expand parameter descriptions with format, range, and constraints. E.g., 'start_date (ISO 8601, e.g., 2025-01-15T09:00:00Z), earliest date to search' and 'query (1-500 chars, free-form text), knowledge base search term'.
• Add error handling guidance to schedule_meeting: 'If overlap detected, call get_free_slots() to find available times. If booking fails, retry after 5 seconds.'
• Add tool annotations: schedule_meeting with destructiveHint=true; get_free_slots and get_booked_slots with readOnlyHint=true. This signals safety to agents.
• Clarify idempotency: does schedule_meeting with identical parameters create a duplicate or return the existing meeting? Document this to guide agent retry logic.