Single tool 'get-world-weather' with minimal description and basic parameter documentation. The tool has a valid schema with proper constraints (latitude -90 to 90, longitude -180 to 180), but the description is too short (10 chars in English, though 'Get world weather' is implied by the Chinese description). No output schema documented. Error handling returns generic messages without recovery guidance. Tool does not follow composite naming pattern (verb_noun is present but description is insufficient). Missing critical pattern implementations: no pagination, no structured output guidance, no error classification, no permission gates.

• Expand tool description to 50-150 characters in English explaining WHAT the tool does, WHEN to use it, and what it returns. Example: 'Get current weather and 16-day forecast for any location worldwide. Provide latitude (-90 to 90) and longitude (-180 to 180). Returns current conditions, hourly temperature/precipitation, and daily weather codes.'
• Document the output schema explicitly. Specify that the response includes 'current_weather' (object with temperature, wind speed), 'hourly' (array of temperatures and precipitation), and 'daily' (array of max/min temps and weather codes). Indicate which fields are most useful for chat interactions.
• Implement error recovery guidance. For HTTP errors, suggest 'Coordinates may be out of range. Ensure latitude is -90 to 90 and longitude is -180 to 180.' For network timeouts, suggest retrying or checking the open-meteo service status.
• Add result size documentation. Specify the response includes 16 days of forecast data (~50-100 KB typically). Suggest calling with specific use cases (e.g., 'Get today's forecast' vs 'Compare 10-day trends') to avoid overwhelming context.
• Enhance parameter descriptions to English. Add usage context: 'latitude: Geographic latitude in decimal degrees (-90 south pole to +90 north pole)' and 'longitude: Geographic longitude in decimal degrees (-180 west to +180 east).'
• Strip and reshape API response. Instead of returning raw JSON, extract and format key fields: current temperature, precipitation chance, weather description (clear/cloudy/rain), and daily high/low. Return as structured text or markdown table for better LLM consumption.