Three tools with basic descriptions and partial schemas. All tools have verb-noun naming (search_, lookup_, get_) which is good. However, descriptions lack depth on WHEN to use each tool and what distinguishes them. Input schemas are present but minimal, parameters have types and basic descriptions, but lack constraints (enums, ranges, patterns). No output schemas documented. Error handling guidance is absent. The server reads like a thin wrapper over a course catalog API rather than an agent-optimized tool interface.

• Document output schemas for all three tools. Specify what fields search_catalog returns (e.g., course_code, title, description, prerequisites, credits), what lookup_schedule returns (term, days, time, location, instructor, seats_available), and what get_academic_calendar returns (term, instruction_start, instruction_end, finals_start, finals_end, priority_enrollment_date).
• Add WHEN-to-use guidance to each description. E.g., 'Use search_catalog to find courses by topic or code. Use lookup_schedule to check when a specific course is offered. Use get_academic_calendar to see registration deadlines and exam dates.'
• Replace example values with formal constraints. For 'term' parameters, define an enum: ['Fall 2025', 'Winter 2026', 'Spring 2026', 'Summer 2026'] or a pattern like '^(Fall|Winter|Spring|Summer) \d{4}$'.
• Add error recovery hints. E.g., 'If no courses match your query, try a broader topic or a course code. If a term is not found, call get_academic_calendar to see available terms.'
• Document pagination and result limits. If search_catalog can return many results, add limit and offset parameters and document the maximum result count (e.g., 'Returns up to 20 courses; use offset to paginate').