Two tools with basic verb-noun naming (get_alerts, get_forecast). Both have short descriptions (47 and 44 chars respectively) that meet minimum but lack context on when to use them or what they return. Input schemas are present with proper types and descriptions. However, output schemas are completely undocumented, tools return plain strings with no structured format guidance. No error handling guidance, no pagination support, no output field documentation. Follows minimal patterns; typical of community STDIO servers.

• Add structured output schemas. Document that get_alerts returns {alerts: [{event, area, severity, description, instructions}], count: int} and get_forecast returns {periods: [{name, temperature, unit, wind_speed, wind_direction, forecast}], location: {lat, lon}}.
• Expand descriptions to 100-150 chars. Example: 'Get active weather alerts for a US state. Returns event type, affected area, severity level, and instructions. Use this to warn users of severe weather, floods, or tornado watches.'
• Add error recovery guidance. Replace 'Unable to fetch alerts' with 'No alerts found for this state. If the state code is invalid, use a two-letter code (CA, NY, TX). If the API is down, retry in 30 seconds.'
• Add parameter constraints. State: enum [AL, AK, AZ, ...] or pattern '^[A-Z]{2}$'. Latitude: number, minimum -90, maximum 90. Longitude: number, minimum -180, maximum 180.
• Document result limits and pagination. Add optional 'limit' parameter (default 20, max 100) to get_alerts. Return {alerts: [...], total_count: int, has_more: bool} to enable pagination.