The weather server defines 2 tools with basic structure but significant quality gaps. Both tools have descriptions and schemas, but descriptions are minimal (18-28 chars, well below the 194-char baseline). Parameters lack meaningful descriptions, 'state' says 'Two-letter state code (e.g. CA, NY)' which includes a discouraged example; 'latitude' and 'longitude' descriptions are truncated in the source and appear incomplete. No documented output schemas, no error handling guidance, no pagination support despite weather alerts potentially returning large result sets. Tool definitions are directly visible in server/src/index.ts via server.tool() registration, so they are not inferred. The code uses Zod schemas with basic validation (e.g., z.string().length(2)), which is good, but no enums, no min/max bounds for lat/long are enforced in the visible schema definitions. Error responses are plain text with no recovery guidance (e.g., 'Failed to retrieve alerts data' tells the LLM nothing). No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite both being read-only operations. No composition risk, tools are single-purpose. Overall: structurally present but minimal in detail.

• Expand tool descriptions to 150 - 200 chars. Example: 'get-alerts: Fetch active weather alerts for a U.S. state via the National Weather Service API. Returns event type, area, severity (low/medium/high/extreme), headline, and effective/expiration times. Use this to answer questions about current warnings or advisories in a region. Requires a 2-letter state code (e.g., CA).'
• Document the output schema explicitly. For get-alerts, describe the structure: { alerts: [ { event, areaDesc, severity, status, headline, effective, expires } ], count }. For get-forecast, describe: { periods: [ { number, name, temperature, temperatureUnit, windSpeed, windDirection, shortForecast } ], location }.
• Remove example values from parameter descriptions. Replace 'Two-letter state code (e.g. CA, NY)' with 'Two-letter U.S. state code (uppercase: AL, AK, AZ, AR, CA, ..., WY)' or use an enum list or link to valid codes.
• Add readOnlyHint to both tool schemas to declare them as safe to retry. In Zod or JSON Schema, add a 'x-readOnly' or equivalent annotation.
• Enhance error responses with actionable guidance. Instead of 'Failed to retrieve alerts data', return: 'Weather Service API unavailable (HTTP 503). Retry in 30 seconds. If error persists, verify the state code is valid (2-letter U.S. state abbreviation).'
• Add optional limit and offset parameters to get-alerts (default limit=20, enforce max=100). Document: 'Returns up to {limit} alerts; use offset for pagination. Total count provided in response.'
• Add parameter descriptions for latitude/longitude with full constraints: 'Latitude (range -90 to 90, required for NWS API point lookup)' and 'Longitude (range -180 to 180, required for NWS API point lookup)'.