Two tools with basic verb-noun naming (getWeatherForecastByLocation, getAlerts) but descriptions are minimal (under 100 chars). Input schemas present with type declarations but parameter descriptions are extremely terse (10-15 chars). No output schema documented. No error handling guidance, no pagination support, no idempotency hints. Tool definitions inferred from WeatherService.java method signatures rather than explicit MCP registration visible in code. Missing critical context: what fields are returned? What errors can occur? When should each tool be called vs the other?

• Document output schemas for both tools. Specify: What fields does getWeatherForecastByLocation return? (e.g., temperature, humidity, wind_speed, forecast_days). What does getAlerts return? (e.g., alert_type, severity, description, affected_counties).
• Expand parameter descriptions to 50-100 chars with constraints. E.g., 'Latitude coordinate (-90 to 90, decimal degrees)' and 'Two-letter US state code (e.g., CA, NY, TX, uppercase only)'.
• Add error handling guidance in tool descriptions. E.g., 'Returns error if latitude/longitude out of bounds or if state code is invalid. Try search_states() to find valid codes.'
• Clarify tool selection criteria. E.g., 'Use getWeatherForecastByLocation for detailed forecasts at a specific location. Use getAlerts for active weather warnings affecting a state.'
• Consider adding pagination or result limits to getAlerts if it can return many alerts. Document max results and whether pagination is supported.