Server has 4 tools with basic schemas and descriptions, but significant quality gaps. Two tools are duplicates (get_alerts appears twice with minor description differences). Descriptions are present but generic (10-50 chars, below the 50-200 char LLM-optimized baseline). Parameters lack detailed constraints (no enums, ranges, or format specifications). No output schemas documented. Error handling is minimal, tools return plain strings without structured guidance. No tool annotations (readOnlyHint, etc.). The echo_resource tool appears to be a test artifact unrelated to weather domain.

• Remove the duplicate get_alerts definition. Keep only the one in server.py with a complete, LLM-optimized description (50-200 chars): 'Retrieve active weather alerts for a US state. Returns event type, severity, affected area, and instructions. Use this to check for warnings before planning outdoor activities.'
• Add parameter constraints: state as enum of valid US state codes (CA, NY, TX, etc.); latitude as number with minimum -90, maximum 90; longitude as number with minimum -180, maximum 180.
• Document output schemas. For get_forecast, return a structured object: {periods: [{name, temperature, temperatureUnit, windSpeed, windDirection, detailedForecast}], location: {latitude, longitude}}. For get_alerts, return {alerts: [{event, area, severity, description, instructions}], state, count}.
• Enhance error messages with recovery guidance. Instead of 'Unable to fetch alerts', return 'No alerts found for CA. Check the state code (e.g., CA, NY, TX) or try a different state.' This guides LLM retry logic.
• Remove echo_resource or document its purpose. If it's a test tool, move it to a separate debug server. If it's intentional, rename to reflect weather domain (e.g., format_weather_alert) and document its actual use case.