This template server has critical definition gaps. Tool descriptions are minimal (10-20 chars), below the 20-char floor for scoring. No output schemas are documented. No error handling guidance. The tools are trivial arithmetic operations with no real-world applicability, but even as a template, they fail to model best practices for LLM-facing tool design.

• Add parameter descriptions to both tools. Example: 'a': {'type': 'int', 'description': 'The first number to add (integer, no limit)'}. Every parameter must explain what it controls.
• Expand tool descriptions to 50-200 characters. Example for add: 'Add two integers and return their sum. Use this for arithmetic calculations. Returns the result as an integer. Handles overflow by Python's arbitrary precision.'
• Document output schemas explicitly. Declare that both tools return an integer result. Include example outputs in the tool definition or docstring.
• Add input validation and error messages. Example: catch OverflowError or TypeError and return 'Invalid input: both a and b must be integers. Got a={type(a).__name__}, b={type(b).__name__}.'
• Rename tools with clearer action verbs: 'calculate_sum' and 'calculate_difference' instead of bare 'add' and 'subtract'. This improves LLM disambiguation in larger tool sets.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry