Two tools with basic schemas and descriptions, but significant gaps in parameter documentation and output schema specification. Tool names follow verb_noun convention (getWeatherForecastByLocation, getAlerts), but descriptions lack depth on when/why to use each tool and what they return. Parameter descriptions exist but are minimal (e.g., 'Latitude coordinate' for latitude). No documented output schemas, error handling guidance, or pagination support. No tool annotations (readOnlyHint, etc.) despite both being read-only operations.

• Document output schemas for both tools. Example: 'Returns {forecast: string, temperature: number, humidity: number, wind_speed: number, timestamp: string}'.
• Expand tool descriptions to 100-200 chars. Include: what data is returned, when to call this vs alternatives, any prerequisites. Example: 'Retrieves current weather forecast for given coordinates from weather.gov. Returns temperature, humidity, wind speed, and forecast text. Use this when you have lat/lon; use getAlerts for state-level warnings.'
• Add format constraints to parameters. Example: 'latitude: number between -90 and 90 (decimal degrees)' and 'state: Two-letter US state code (e.g., CA, NY, TX). Must be uppercase.'
• Add tool annotations via Spring AI: @Tool(description=..., readOnlyHint=true) to signal these are safe, non-destructive operations.
• Add error handling examples in descriptions: 'If coordinates are out of range or API is unavailable, returns error with retry guidance. If state code is invalid, returns list of valid state codes.'