This server has critical gaps in definition quality. Both tools have non-English names and minimal descriptions that lack essential context. Tool schemas are present but parameter descriptions are very brief. The naming violates LLM conventions by using Chinese characters instead of English verb-noun patterns, making tool discovery and selection impossible for most LLM agents. Descriptions are under 30 characters each, providing almost no guidance on when or how to use these tools. Error handling and output schemas are not documented.

• CRITICAL: Rename tools to English verb-noun patterns: '获得天气信息警报' → 'get_weather_alerts' and '获取天气预测' → 'get_weather_forecast'. Tool names are the primary signal LLMs use for discovery.
• CRITICAL: Expand tool descriptions to 50-200 chars. Example: 'get_weather_alerts: Retrieve active weather alerts and warnings for a US state. Use this to check for severe weather conditions, storms, or advisories. Returns alert type, severity, and affected areas.' This tells the LLM WHAT, WHEN, and WHY.
• Expand parameter descriptions. For 'state', add: 'Two-letter US state code (e.g., CA, NY, TX). Must be a valid USPS state abbreviation.' For 'latitude'/'longitude', add: 'Decimal degrees (WGS84 coordinate system). Latitude range -90 to +90, longitude range -180 to +180.'
• Document the return schema for each tool. Example: 'Returns: { conditions: string, temperature_celsius: number, humidity_percent: number, wind_kmh: number, last_updated: ISO8601_string, alert_count: number }'. This lets LLMs know what to extract.
• Add error handling guidance. Example: 'If state code is invalid, returns error 400 with message "Invalid state code. Must be 2-letter US state abbreviation (e.g., CA, NY)." LLM should retry with a valid code.' Reference the recovery-guide pattern.
• Convert 'state' parameter to an enum listing all valid US state codes, or at least document the constraint in the description with a regex pattern or validation rule.
• Add pagination support if these tools can return large result sets (e.g., many alerts or forecast days). Include 'limit' and 'offset' parameters and document max result limits.