Single tool 'getWeather' has critical definition gaps. Input schema present but parameters lack descriptions (null values). Tool description missing entirely. No output schema documented. Error handling returns generic 'Error' string without recovery guidance. Naming is acceptable (verb_noun pattern) but insufficient to overcome missing descriptions and schemas.

• Add a tool description (50-200 chars): 'Fetch current weather and hourly forecast for a geographic location. Provide latitude and longitude coordinates. Returns temperature, wind speed, and humidity data.'
• Add parameter descriptions: lat='Latitude coordinate (-90 to 90, decimal format, e.g. 40.7128)', lng='Longitude coordinate (-180 to 180, decimal format, e.g. -74.0060)'
• Document the output schema in code comments or a separate schema definition showing returned fields: current.temperature_2m, current.wind_speed_10m, hourly array structure, etc.
• Improve error handling to return structured errors with recovery hints: '{"error": "Invalid coordinates", "hint": "Latitude must be between -90 and 90; longitude between -180 and 180"}' instead of generic 'Error'
• Add input validation before API call to catch invalid lat/lng early and return actionable error messages that guide the LLM to correct values