This MCP server defines 3 simple arithmetic and weather tools using FastMCP. All tools have minimal but present descriptions and basic input schemas. However, the descriptions are extremely terse (10-28 characters), falling well below the baseline of 194 characters. No output schemas are documented. Parameters lack detailed guidance on valid ranges, formats, or constraints. Error handling is absent, there is no recovery guidance, actionable error messages, or validation hints. The tools are purely read-only utility functions with no state mutation, but the lack of comprehensive documentation and error handling severely limits production readiness. The server demonstrates basic tool registration but lacks the depth expected of production-grade tools.

• Expand all tool descriptions to 100-300 characters. Include: what the tool does, when to use it vs alternatives, what it returns, and any prerequisites or constraints. Example: 'add(a, b) returns the sum of two integers in range [-1M, 1M]. Use when you need basic arithmetic; for complex calculations, break into multiple calls.'
• Document output schemas explicitly. For add and multiply, specify: 'Returns an integer result in range [-2M, 2M].' For get_weather, specify: 'Returns a JSON object: {location: string, condition: string, temperature_f?: number, forecast?: string}. If data unavailable, returns error with suggested alternatives.'
• Add parameter constraints in descriptions. Example for a/b: 'Integer in range -1,000,000 to 1,000,000. Defaults to 0 if omitted (if you make them optional).' Example for location: 'String, one of: nyc, sf, la, boston, chicago, denver, seattle. Case-insensitive. If your location is not listed, use search_weather_locations() first.'
• Implement structured error handling. When get_weather receives an unknown location, return: {success: false, error: 'Location not supported. Available: nyc, sf, la, boston...', recovery_hint: 'Try one of the available locations, or call search_weather_locations() for your region.'}
• Add validation inside tool implementations. For add/multiply, validate that a and b are within [-1M, 1M] and return a clear error if not. For get_weather, validate that location is in the supported list before processing.
• Document edge cases and failure modes. What happens if an LLM passes null, NaN, or infinity to add? What if location is an empty string or extremely long? Provide explicit guards and error messages.