Two tools with basic but incomplete definitions. Both have action-verb names (get-alerts, get-forecast) and descriptions present. Input schemas are visible with Zod validation (state length constraint, latitude/longitude bounds). However, descriptions are minimal (under 100 chars), lack context on when to use each tool, and output schemas are not documented. No error handling guidance. Parameters have descriptions but lack detail on expected formats or failure modes. Schemas are present but sparse.

• Document output schemas for both tools. Specify fields returned (e.g., for get-alerts: event, areaDesc, severity, status, headline; for get-forecast: periods array with temperature, windSpeed, shortForecast).
• Expand descriptions to 100-200 chars. Include when to use (e.g., 'Call get-alerts to check for active weather warnings in a US state before planning outdoor activities') and what to expect.
• Add error recovery guidance. Replace 'Failed to retrieve alerts data' with 'No alerts available for this state. State code must be a valid 2-letter US state abbreviation (e.g., CA, NY, TX).'
• Add pagination to get-alerts. Include optional limit (default 20, max 100) and offset parameters. Return total count so LLM knows if more results exist.
• Enhance parameter descriptions with format details. For state: 'Two-letter US state code (uppercase, e.g., CA, NY, TX)'. For coordinates: 'Latitude/longitude in decimal degrees (e.g., 37.7749, -122.4194 for San Francisco). Precision to 4 decimals recommended.'