Two tools with clear verb-noun naming (get-alerts, get-forecast) and basic parameter schemas using Zod. Both tools have short descriptions (under 50 chars) that lack context for LLM selection. Parameter descriptions are present but minimal. No output schema documentation. Error handling returns text responses but lacks actionable recovery guidance. No tool annotations (readOnlyHint, etc.). Schemas are properly typed with constraints (lat/lon bounds, state length), but descriptions do not explain when to use each tool or what the output structure contains.

• Expand tool descriptions to 100-200 chars. Example: 'Get active weather alerts for a US state. Returns event type, severity, area, and headline. Use this to check for warnings before get-forecast. Requires two-letter state code (CA, NY, etc.).'
• Document output schema explicitly. Define that get-alerts returns {alerts: [{event, area, severity, status, headline}]} and get-forecast returns {forecast: [{name, temperature, windSpeed, shortForecast}]}.
• Add error classification and recovery hints. Instead of 'Failed to retrieve alerts data', return 'No alerts available for state (retryable)' or 'State code invalid, must be 2-letter US state code (user-fixable)'.
• Add tool annotations to schema: readOnlyHint: true and idempotentHint: true for both tools. This signals to agents that calls are safe to retry.
• Replace example values in descriptions with enum constraints. For state parameter, consider accepting both codes (CA) and full names (California) via a lookup, or document the exact enum of valid state codes.