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 (lat/lon bounds, state length) but lack depth. Output is unstructured text rather than typed objects. No error recovery guidance, no pagination, no output schema documentation. Schemas are visible and properly constrained, but descriptions fall short of LLM-optimization standards (target 50-200 chars per pattern:tool-description).

• Expand tool descriptions to 80-150 chars. Example for get_alerts: 'Retrieve active weather alerts for a US state. Returns event type, severity, affected area, and headline. Useful for checking warnings before travel or outdoor activities.'
• Return structured JSON objects instead of formatted text. get_alerts should return {alerts: [{event, severity, area, headline, status}], total_count, state_code}. get_forecast should return {location: {lat, lon}, periods: [{name, temp, wind, forecast}]}.
• Add limit and offset parameters to get_alerts. Default limit=20, max=100. Include total_count in response for pagination awareness.
• Enhance error messages with recovery hints. E.g., 'Invalid state code: got "XX". Valid codes: CA, NY, TX, ... (all 50 US states).' or 'Coordinates outside US. NWS API only supports US locations.'
• Document parameter constraints in descriptions. E.g., 'latitude: -90 to 90 (decimal degrees)' and 'state: exactly 2 uppercase letters (e.g., CA, NY)'.