Two tools with basic verb-noun naming (get_alerts, get_forecast). Both have short descriptions (34-45 chars, below the 194-char baseline). Input schemas present with proper JSON Schema structure and typed parameters. However, parameter descriptions are minimal (8-40 chars vs 72-char baseline), and output schemas are not documented. No error handling guidance, no pagination support despite potential for large result sets, and no tool annotations. Naming is acceptable but descriptions and parameter documentation fall significantly short of production baselines.

• Expand tool descriptions to 100-200 chars. Example: 'Get active weather alerts for a US state. Returns alert type, severity, affected areas, and issue time. Use this to check for warnings before planning outdoor activities or travel.'
• Add parameter descriptions with constraints. For latitude/longitude: 'Latitude in decimal degrees (-90 to 90). Use negative for Southern Hemisphere.' For state: 'Two-letter US state code (e.g., CA, NY, TX). Case-insensitive.'
• Document output schema in tool description or as a separate schema field. Example: 'Returns array of {alert_id, type, severity, description, issued_at, expires_at, affected_areas}.'
• Add error handling guidance. Example: 'If state code is invalid, returns error with list of valid codes. If coordinates are out of bounds, returns error with valid range.'
• Add limit and offset parameters to support pagination. Example: 'limit (1-100, default 20) and offset (default 0) to paginate large result sets.'