The Weather MCP server provides two functional tools with explicit descriptions and input schemas. Both tools have acceptable naming (verb_noun pattern: get_alerts, get_forecast) and documented parameters. However, the definitions have significant gaps that prevent higher scores: (1) parameter descriptions lack detail on constraints and formats (e.g., state code validation, latitude/longitude bounds); (2) output schemas are completely undocumented, the tools return plain strings rather than structured objects, making it impossible for LLMs to chain results or extract specific fields; (3) error handling is minimal with generic fallback messages that don't guide recovery; (4) no pagination support despite potentially returning variable-length alert lists; (5) tool descriptions are functional but brief (18 - 24 chars), missing context on when to use each tool or dependencies between them. The server shows basic competence but lacks the rigor expected of production tools.

• Document output schemas explicitly. Define both tools to return structured objects: get_alerts → { alerts: [{ event: string, area: string, severity: string, description: string, instruction: string }], total: int, limited: bool }; get_forecast → { periods: [{ name: string, temperature: int, temperatureUnit: string, windSpeed: string, windDirection: string, detailedForecast: string }], nextPeriods: string | null }.
• Add parameter constraints to descriptions: state → 'Two-letter US state code in uppercase (e.g., CA, NY, TX). Must be a valid FIPS state code.' latitude → 'Latitude in decimal degrees (-90 to 90). Coordinates outside continental US will return no results.' longitude → 'Longitude in decimal degrees (-180 to 180).'
• Implement result pagination for get_alerts. Add optional parameters: limit (1 - 100, default 20) and offset (0+). Return total alert count and a hasMore flag so agents can fetch additional alerts if needed.
• Enhance error messages with recovery hints. Instead of 'Unable to fetch alerts or no alerts found', return structured errors: { error: 'invalid_state', message: 'State code "XX" is not valid. Use two-letter FIPS code (e.g., CA, NY).', hint: 'Check state spelling or use list_states tool to see valid options.' } or { error: 'location_not_in_us', message: 'No forecast data available for the provided coordinates.', hint: 'Coordinates must be within the continental US for NWS data. Try a US location.' }
• Expand tool descriptions to 50 - 100 characters, including context: get_alerts → 'Retrieve active weather alerts (severe storms, floods, etc.) for a US state. Use when the user asks about hazards or warnings in a specific state.' get_forecast → 'Get detailed weather forecast (temperature, wind, conditions) for a specific location (latitude/longitude). Use after get_alerts to show upcoming conditions or when user specifies coordinates.'