Two tools with clear verb-noun naming (get_current_weather, get_forecast) and basic descriptions. Schemas are present with Zod validation and parameter descriptions. However, descriptions are minimal (34-50 chars, below the 50-200 char LLM-optimized baseline), output schemas are not documented, and error handling lacks recovery guidance. Tool definitions are visible in weather-mcp/src/index.ts with explicit registration via this.server.tool().

• Expand tool descriptions to 80-150 chars. Example: 'Get current weather for a city including temperature (°C/°F), conditions, wind speed, and humidity. Call this for real-time conditions; use get_forecast for multi-day outlook. Accepts city name or 'City, Country' format.'
• Document output schemas in tool descriptions or as a separate schema field. Example: 'Returns {location: string, temperature_c: number, temperature_f: number, conditions: string, wind_kph: number, humidity_pct: number}'.
• Enhance error messages with recovery hints. When geocoding fails, return: 'Location not found. Try a more specific format like "London, UK" or "Austin, TX", or call get_forecast to see available regions.'
• Add explicit range documentation to get_forecast 'days' parameter description: 'Number of days to forecast (1-7, default 5)' instead of relying on Zod schema alone.
• Add tool annotations to the MCP schema registration: mark both tools with readOnlyHint=true and idempotentHint=true to signal safety to clients.