Two tools with minimal descriptions (10-20 chars each) and incomplete parameter documentation. Tool names lack action verbs (forecast, forecast_grid are nouns). Input schemas present but parameters lack descriptions, LLMs cannot infer what 'exclude', 'extend', 'lang', 'units' control. No output schema documented. No error handling guidance. API key exposed as parameter (_apiKey), violating secret-injection pattern. No pagination, result limits, or structured output guidance.

• Rename tools to action verbs: 'get_forecast' and 'get_grid_forecast'. This signals intent and helps LLMs disambiguate from similar tools.
• Move API key to server-side secret injection. Read PIRATE_WEATHER_API_KEY from environment; remove _apiKey parameter. Update callTool to use process.env.PIRATE_WEATHER_API_KEY with a clear error if missing.
• Add parameter descriptions: 'exclude' (comma-separated data blocks to omit: currently, minutely, hourly, daily, alerts), 'extend' (extend hourly forecast to 7 days), 'lang' (language code for text fields), 'units' (us|si|ca|uk|uk2, unit system for temperature, wind, pressure).
• Document output schema in tool description or as a separate schema field. Specify that forecast returns {currently, minutely, hourly, daily, alerts, flags} with typed fields (temperature: number, time: ISO 8601 string, etc.).
• Enhance error messages with recovery guidance: 'Invalid API key. Verify PIRATE_WEATHER_API_KEY is set and valid (free at https://pirate-weather.apiable.io).' For rate limits, suggest retry with exponential backoff.