Two tools with basic verb-noun naming (get_alerts, get_forecast). Both have short descriptions (40-50 chars) and documented input schemas with type info. However, descriptions lack context on WHEN to use each tool, what they return, and any prerequisites. No output schema documentation. Parameters have types and brief descriptions but lack constraints (e.g., state code format, lat/lon ranges). Error handling returns plain strings with no recovery guidance. No pagination, no structured output, no tool annotations.

• Expand tool descriptions to 100-150 chars. Example: 'Get active weather alerts for a US state (2-letter code). Returns event type, severity, area, and instructions. Use this to warn users of storms, floods, or other hazards.'
• Document output schema explicitly. Define return type as JSON object with fields: alerts (array of {event, area, severity, description, instructions}) or forecast_periods (array of {name, temperature, wind, forecast}).
• Add parameter constraints in descriptions. For state: 'Two-letter US state code (uppercase, e.g. CA, NY, TX)'. For lat/lon: 'Latitude -90 to 90, longitude -180 to 180, decimal precision to 4 places.'
• Improve error messages with recovery hints. Instead of 'Unable to fetch alerts', return 'Failed to fetch alerts for state code {state}. Verify the code is valid (e.g. CA, NY). If the issue persists, the NWS API may be temporarily unavailable, try again in a few minutes.'
• Document the 5-period limit in get_forecast description and consider adding an optional 'periods' parameter (default 5, max 14) to let users request longer forecasts.