Two tools with basic verb-noun naming (get_alerts, get_forecast). Both have short descriptions (40-50 chars) and documented input schemas with types. However, descriptions lack context on WHEN to use each tool, prerequisites, or what the output contains. No output schema documentation. Parameters have types and brief descriptions but lack constraints (e.g., state code format, lat/lon ranges). Error handling returns plain strings with no recovery guidance. No pagination, no structured output, no tool annotations.

• Expand descriptions to 100-150 chars. Example: 'Get active weather alerts for a US state. Returns event type, severity, area, and instructions. Call this to check for warnings before planning outdoor activities.'
• Add output schema documentation. Specify that tools return formatted strings with fields like event, severity, area, description. Consider returning structured JSON instead of plain text for better LLM parsing.
• Add parameter constraints: state as enum of valid 2-letter codes or regex pattern '^[A-Z]{2}$'; latitude as number with min -90, max 90; longitude as number with min -180, max 180.
• Improve error messages with recovery guidance. Example: 'State code invalid. Must be 2-letter US state code (e.g., CA, NY). Got: "XX". Try again with a valid code.'
• Add tool annotations to schema: readOnlyHint=true for both tools to signal they are safe to call without confirmation.