Server exposes 10 tools with basic schemas and descriptions. All tools have names starting with action verbs (search_, get_, list_) and descriptions present. However, descriptions are minimal (10-50 chars), parameter descriptions lack depth, and output schemas are not documented. No error handling guidance, no tool annotations, and no composition patterns evident. Tools are read-only but lack idempotent hints. Schema quality is moderate, all params have types but lack format constraints, ranges, or validation guidance. This is typical community-grade work: functional but not production-ready.

• Expand tool descriptions to 50-200 chars. Include WHAT the tool does, WHEN to use it (vs similar tools), and WHAT it returns. E.g., 'Get the class schedule for a specific day. Use this to check when a class meets. Returns periods with subject and teacher info.'
• Document output schemas for all tools. Specify field names, types, and whether results are paginated. E.g., 'Returns {schools: [{code: string, name: string, address: string}], total: number}'.
• Add error handling guidance to descriptions. E.g., 'If school_code is invalid, returns 404 with available codes. If date is outside timetable range, returns 400 with available dates.'
• Add tool annotations: mark all tools with readOnlyHint=true and idempotentHint=true so agents know they are safe to retry.
• Add parameter constraints: specify min/max for grade (1-3), class_no (1-20), and date ranges. Use regex patterns or enums where applicable.