Two tools with clear verb-noun naming (get-alerts, get-forecast) and basic parameter schemas using Zod. Descriptions are present but minimal (10-40 chars). Input schemas are properly typed with constraints (lat/lon bounds, state length). However, output schemas are undocumented, LLMs cannot predict response structure. Error handling returns text blobs without actionable guidance. No parameter descriptions beyond the schema constraints. Missing composition guidance (e.g., when to use alerts vs forecast). Typical community server quality.

• 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 2-letter state code (CA, NY, etc).'
• Document output schema in tool description or as a separate schema field. Example: 'Returns {alerts: [{event, severity, areaDesc, headline}], count: number}'
• Add per-parameter descriptions in the Zod schema using .describe(). Example: z.string().length(2).describe('Two-letter US state code (e.g., CA, NY, TX). Case-insensitive.')
• Enhance error messages with recovery guidance. Example: 'Failed to retrieve alerts for CA. This location may not be supported by NWS API (US only). Try a different state code or use get-forecast with lat/lon instead.'
• Add limit parameter to both tools (default 20, max 100) and document in description. Return total count so LLM knows if results are truncated.