Two tools with basic verb-noun naming (get_alerts, get_forecast). Both have descriptions and input schemas with typed parameters. However, descriptions are minimal (10-20 chars), parameter descriptions lack detail on constraints/formats, and output schemas are undocumented. No error handling guidance, no pagination support despite potentially large result sets, and no tool annotations. Schemas are present but sparse, latitude/longitude lack range constraints, state parameter lacks enum of valid codes.

• Expand tool descriptions to 100-200 characters. Example: 'get_alerts: Retrieve active weather alerts for a US state. Returns event type, severity, area, and instructions. Use when user asks about weather warnings or hazards for a specific state (e.g., "What alerts are active in California?").'
• Add enum constraint for state parameter: state must be a two-letter US state code (CA, NY, TX, etc.). Document in parameter description and add to schema.
• Add range constraints for latitude (-90 to 90) and longitude (-180 to 180) in parameter descriptions and JSON Schema.
• Document output schema as structured JSON with fields: alerts (array of {event, area, severity, description, instructions}), total_count, and timestamp. Return JSON instead of plain text.
• Add error handling with actionable messages: 'Invalid state code "XX". Use two-letter abbreviation (e.g., CA, NY).' and 'Location outside US coverage area. Try coordinates within continental US.'