Two tools with basic verb-noun naming (get_alerts, get_forecast). Both have short descriptions (34-40 chars, below the 50-200 char LLM-optimized baseline). Input schemas present with types and descriptions, but output schemas are completely undocumented, tools return plain strings with no structured format. No error handling guidance, no parameter constraints (e.g., state code validation), no pagination support. Descriptions lack WHEN/WHY context and dependency hints. No tool annotations (readOnlyHint, etc.). Overall structure is minimal but functional.

• Document output schemas explicitly. Define get_alerts to return {alerts: [{event, area, severity, description, instructions}], count: int} and get_forecast to return {periods: [{name, temperature, unit, wind_speed, wind_direction, forecast}], location: {lat, lon}}.
• Expand descriptions to 80-150 chars. Example: 'Get active weather alerts for a US state. Returns event type, severity, affected area, and instructions. Call this to check for warnings before travel or outdoor activities.'
• Add state parameter as enum with valid 2-letter US codes (AL, AK, AZ, ..., WY). Add latitude/longitude constraints: latitude -90 to 90, longitude -180 to 180.
• Add readOnlyHint: true to both tools in schema. Include error recovery guidance: 'If location not found, verify latitude/longitude are within ±90/±180. If state code invalid, use 2-letter abbreviation (CA, NY, TX, etc.)'
• Add limit and offset parameters to get_forecast. Return total period count and next_offset. Document: 'Limit defaults to 5 periods; max 14. Use offset for pagination.'