This server defines 2 tools with basic but incomplete implementation. Both tools have acceptable names starting with action verbs (get-alerts, get-forecast) and short descriptions (34-46 chars, within the 10-1024 baseline). Input schemas are present and use Zod with type constraints. However, critical gaps exist: output schemas are completely undocumented (tools return unstructured text only, no structured response field contracts), error handling lacks guidance for LLM recovery, no pagination support despite potentially large result sets, and parameter descriptions are minimal. The tool descriptions answer 'what it does' but lack 'when to use it' and 'prerequisites' context. Most concerning: both tools return raw text concatenation rather than structured objects, violating the pattern:response-shaper rule. The server would receive a code review with findings about response structure and error guidance.

• Document output schema for each tool. Define structured response objects with typed fields. Example for get-alerts: { alerts: Array<{ event: string, area: string, severity: string, status: string, headline: string }>, count: number }. Example for get-forecast: { location: string, periods: Array<{ name: string, temperature: number, unit: string, windSpeed: string, windDirection: string, forecast: string }> }.
• Enhance error messages with actionable recovery guidance. Example: 'Failed to retrieve alerts for state code: Invalid state code. State must be a valid 2-letter US state abbreviation. Available states: AL, AK, AZ, ...' or 'Failed to retrieve forecast: Location outside US coverage area. NWS API only supports US coordinates (including territories).'
• Add prerequisites and context to tool descriptions. Example: 'Get active weather alerts for a US state. Returns all active alerts issued by the National Weather Service for the specified state. Prerequisite: state must be a valid 2-letter US state code (CA, NY, TX, etc.). Use this when the user asks about severe weather, warnings, or active emergencies in a region.'
• Remove example values from parameter descriptions. Replace 'Two-letter state code (e.g. CA, NY)' with 'Two-letter US state code. Valid codes: AL, AK, AZ, AR, CA, CO, CT, DE, FL, GA, HI, ID, IL, IN, IA, KS, KY, LA, ME, MD, MA, MI, MN, MS, MO, MT, NE, NV, NH, NJ, NM, NY, NC, ND, OH, OK, OR, PA, RI, SC, SD, TN, TX, UT, VT, VA, WA, WV, WI, WY' or use enum constraint if schema supports it.