Two tools with basic schemas and minimal descriptions. Both tools have input schemas with proper types (number, string, enum), but descriptions are extremely short (10-50 chars) and lack context for LLM selection. No output schema documentation. No error handling guidance beyond a single divide-by-zero check. Tool names lack action verbs (add, calculate are weak; should be compute_sum, perform_calculation). Parameters lack descriptions entirely in the schema, only visible in Zod definitions, not in formal parameter documentation. No pagination, no structured output guidance, no recovery hints.

• Expand tool descriptions to 50-200 chars. For 'add': 'Adds two numbers and returns their sum. Use when you need basic arithmetic addition.' For 'calculate': 'Performs arithmetic operations (add, subtract, multiply, divide) on two numbers. Use for complex calculations or when operation type is dynamic.'
• Add parameter descriptions to schema. Each parameter (a, b, operation) needs a description: 'a: First operand (number)', 'b: Second operand (number)', 'operation: Arithmetic operation to perform (add|subtract|multiply|divide)'.
• Document output schema explicitly. E.g., 'Returns: {result: number}, the computed result as a numeric value.'
• Rename tools to action verbs: 'compute_sum' (for add) and 'perform_arithmetic' (for calculate). This clarifies intent and helps LLMs select the right tool.
• Enhance error handling: validate inputs (reject NaN, Infinity), return structured error responses with recovery hints (e.g., 'Invalid operation: got "modulo", must be one of: add, subtract, multiply, divide').