Server provides 2 simple calculator tools with basic schemas and descriptions. Both tools have input schemas (Zod-validated, converted to JSON Schema) and descriptions present. However, descriptions are very short (10-34 chars, well below the 50-200 char LLM-optimized baseline), lack actionable context (no WHEN to use, no error guidance), and are missing detail about what the tool returns. Parameter descriptions exist but are minimal (7-34 chars). No output schema documentation. Error handling is present for divide-by-zero but not generalized. Tools pass basic definition checks but fall short of production quality standards. Average of per-tool scores: (52 + 64) / 2 = 58.

• Expand tool descriptions to 50-200 chars, following the pattern: 'Adds two numbers and returns the result as a string. Use when you need basic addition. Returns the sum in plain text format.' This helps LLMs understand WHEN to call add vs calculate.
• Add full output schema documentation in tool registration or comments. Document that both tools return {content: [{type: 'text', text: string}]}.
• Enhance parameter descriptions: 'First operand (any real number)' instead of 'First number to add'. Include range, type, and any constraints.
• Rename 'calculate' to 'arithmetic_operation' or 'compute_arithmetic' to avoid ambiguity. The name alone should convey support for multiple operations.
• Add general error handling with actionable messages. For divide-by-zero, return 'Cannot divide by zero. Try a non-zero divisor.' For invalid operation enum (if somehow passed), return 'Invalid operation: got "<value>", must be one of: add, subtract, multiply, divide'.
• Document that both tools are READ_ONLY and idempotent (safe to retry). Consider adding toolAnnotations (readOnlyHint, idempotentHint) if SDK supports them.