Two tools with clear verb-noun naming (get_alerts, get_forecast) and basic parameter schemas using Zod. Descriptions are present but minimal (10-40 chars). Parameters have type constraints (latitude/longitude bounds, state length) but lack depth. No output schema documentation. Error handling returns text responses but lacks actionable recovery guidance. Missing parameter descriptions for some fields and no documentation of response structure.

• Expand tool descriptions to 80-150 chars. Example: 'get_alerts: Retrieve active weather alerts for a US state (2-letter code). Returns event type, severity, affected area, and headline. Use when user asks about weather warnings or hazards.'
• Document output schema in tool descriptions or as structured comments. Specify that get_alerts returns {features: [{properties: {event, areaDesc, severity, status, headline}}]} and get_forecast returns {periods: [{name, temperature, temperatureUnit, windSpeed, windDirection, shortForecast}]}.
• Add error classification to responses. Return structured errors: {error: 'location_unsupported', message: 'Coordinates outside US. NWS API only covers continental US.', retryable: false}. This guides LLM recovery.
• Add limit parameter (default 20, max 100) to both tools to cap results and prevent context bloat. Document in description: 'Returns up to [limit] alerts/periods.'
• Provide enum or validation for state parameter. Document: 'state: Two-letter US state code (AL, AK, AZ, ... WY). Invalid codes return error with list of valid codes.'