Three tools with minimal definitions. All have basic verb-noun naming (add, multiply, get_weather) and short descriptions (10-34 chars), but descriptions lack context on WHEN to use tools or WHAT they return. No parameter descriptions beyond type hints. No output schemas documented. No error handling guidance. Schemas are present but minimal, only type and description at parameter level, no constraints, ranges, or validation rules. This is below the baseline for production tools (avg description 194 chars, avg param annotation 72 chars).

• Expand tool descriptions to 100-200 chars. Example: 'add: Adds two integers and returns their sum. Use when the user asks for arithmetic addition. Returns an integer result.'
• Document output schemas explicitly. Example: 'Returns: {"result": integer, "operation": string}' or inline in docstring.
• Add parameter constraints. Example: 'a (integer, range 0-1000000): The first operand. Must be a whole number.'
• Add error handling guidance. Example for get_weather: 'If location is invalid, returns error with available regions. Retry with a valid location from the list.'
• Clarify get_weather description: 'Retrieves current weather conditions for a specified location. Returns temperature, conditions, and forecast. Use when user asks about weather.'
• Consider adding idempotent/readonly hints via tool annotations (if supported by fastmcp) to signal these are safe, read-only operations.