Single tool 'get-weather' has a valid Zod schema with proper type and description, but the tool description itself is inadequate. The description 'The name of the city to get weather information for' is a parameter description, not a tool description, it fails to explain WHAT the tool does, WHEN to use it, or what it returns. No output schema is documented. Error handling returns plain text in a 'text' field with an isError flag, but provides no recovery guidance. The prompt 'check-weather' is present but does not compensate for tool-level gaps. Overall structure is present but falls short of production quality.

• Add a proper tool description: 'Retrieves current weather information for a specified city. Returns temperature, conditions, humidity, and wind speed. Use this when the user asks about weather in any location.'
• Document the output schema in code comments or a separate schema definition. Example: {temperature: number, condition: string, humidity: number, wind_speed: number, city: string}
• Enhance error messages with recovery guidance. Instead of 'Error fetching weather data: <message>', return 'Failed to fetch weather for <city>. Verify the city name is spelled correctly (e.g., New York, not Newyork). Try a major city name.'
• Add format constraints to the parameter description: 'City name (2-50 characters, e.g., New York, London, Tokyo). Use the full city name or major city abbreviations.'
• Implement input validation: reject empty strings, validate city name length, and return specific error messages for each failure case.