Two tools with basic but incomplete definitions. Both have clear verb-noun naming (get-alerts, get-forecast) and descriptions present. Input schemas are properly typed with Zod validation and include min/max constraints for numeric parameters. However, descriptions are minimal (under 100 chars), lack context about when to use each tool, and output schemas are not documented. No error recovery guidance provided. Parameters lack detailed format descriptions beyond type constraints.

• Expand tool descriptions to 100-200 chars. Example for get-forecast: 'Retrieve a 7-day weather forecast for a US location (latitude/longitude). Returns temperature, wind, and conditions for each period. Only supports US coordinates via National Weather Service API.'
• Document output schemas 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 recovery guidance. Replace 'Failed to retrieve alerts data' with 'Failed to retrieve alerts for {state}. Verify the state code is valid (e.g., CA, NY) and try again. If the issue persists, the NWS API may be temporarily unavailable.'
• Include geographic scope in parameter descriptions. For get-forecast latitude/longitude: 'Must be a valid US location. Non-US coordinates will fail with a 404 error.'
• Add result limits and pagination hints. Document that get-alerts returns all active alerts (typically 0-20) and get-forecast returns 14 periods (7 days × day/night). If results are truncated, explain how to request specific time ranges.