Two tools with basic schemas and descriptions, but significant gaps in parameter documentation and output structure. sum_numbers has minimal description (10 chars); create_employee has better coverage but lacks output schema documentation. Neither tool documents return types formally. Parameters have type annotations but descriptions are sparse. No error handling guidance, no pagination, no idempotency markers. Naming is verb-forward (sum_, create_) but descriptions don't explain WHEN to use each tool or what downstream tools expect.

• Expand sum_numbers description to 50-150 chars: 'Add two integers via external service. Returns their sum. Use for arithmetic operations requiring remote computation. Fails if service is unavailable or inputs are non-integer.'
• Document output schemas explicitly in docstrings: sum_numbers returns {type: int, description: 'Sum of number1 and number2'}; create_employee returns {type: str, description: 'Response from service (e.g., employee ID or success message)'}.
• Replace generic error messages with actionable guidance: 'HTTP Error 503: External service unavailable. Retry in 30 seconds.' or 'Invalid response: expected integer, got "abc". Check service endpoint.'
• Add parameter constraints to create_employee: date_of_birth should document 'YYYY-MM-DD format, e.g. 1990-01-15' and nif should specify 'Non-negative integer, typically 8-12 digits for tax ID'.
• Annotate tools with destructiveHint/readOnlyHint in FastMCP decorator: @mcp.tool(readOnlyHint=True) for sum_numbers; @mcp.tool(destructiveHint=True) for create_employee to signal idempotency and retry safety.