Three tools with basic verb-noun naming (get_*), but descriptions are minimal (10-60 chars, well below the 194-char baseline). Input schemas are present with type declarations but lack descriptions for every parameter. No output schema documentation. Error handling is absent from tool definitions. The server implements a degraded mode when API keys are missing, but this is not surfaced in tool descriptions, leaving agents unaware of functional limitations.

• Expand each tool description to 100 - 200 characters. Include: what the tool does, when to use it (e.g., 'Call this first to find school codes'), and what it returns. Example: 'Search for a school by name and return its code, organization code, and name. Use this to look up school identifiers before calling get_school_schedule.'
• Add descriptions to every parameter. For 'from_date' and 'to_date', write: 'Start/end date in YYYYMMDD format (e.g., 20240101 for Jan 1, 2024). Must be valid dates; future dates may return no results.'
• Document output schemas in tool descriptions or as a separate schema field. Example: 'Returns {valid: bool, message: str, school_num: int, school_name: [str], school_code: [str], org_name: [str], org_code: [str]}.'
• Add a note to all three tools: 'If NEIS_SERVICE_KEY is not configured, results are limited to 5 items. Configure the environment variable for full results.'
• Add error guidance to descriptions. Example: 'If no schools are found, try a partial name or check the school name spelling. If the API returns an error, the service may be temporarily unavailable.'