Two tools with basic verb-noun naming (get_alerts, get_forecast). Both have descriptions and input schemas with typed parameters. However, descriptions are minimal (under 100 chars each), lack context on when to use each tool, and do not explain output structure. Parameters have type definitions but lack constraints (e.g., state format, latitude/longitude bounds). No output schema documented. Error handling returns plain strings without recovery guidance. No tool annotations (readOnlyHint, etc.). Schemas are present but sparse.

• Add output schema documentation. Define get_alerts to return {alerts: [{event, area, severity, description, instructions}]} and get_forecast to return {periods: [{name, temperature, temperatureUnit, windSpeed, windDirection, detailedForecast}]}.
• Expand descriptions to 80-150 chars. Example: 'Get active weather alerts for a US state. Returns event, severity, area, and instructions. Use before forecast to warn of hazards.' Include when to call each tool.
• Add parameter constraints: state as enum of valid 2-letter codes or regex ^[A-Z]{2}$; latitude as number with minimum -90, maximum 90; longitude as number with minimum -180, maximum 180.
• Improve error messages with recovery hints. E.g., 'No alerts found for state CA. Verify state code is valid (e.g., CA, NY, TX). If correct, no active alerts exist.' or 'Forecast unavailable for coordinates (lat, lon). Verify coordinates are within US bounds.'
• Add readOnlyHint: true to both tools in FastMCP decorator to signal they are safe to retry and have no side effects.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry