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-40 chars) and lack context for LLM selection. No output schema documentation. Error handling present (divide-by-zero check) but not comprehensive. Tool names are action-oriented (add, calculate) but lack verb prefixes. No parameter descriptions beyond type hints in schema.

• Expand tool descriptions to 50-200 chars. Example: 'add: Performs simple addition of two numbers. Use when you need to sum two values. Returns the numeric result.' and 'calculate: Performs arithmetic operations (add, subtract, multiply, divide) on two operands. Use for complex calculations. Returns numeric result or error message.'
• Add descriptions to all input parameters in schema. Example: 'a: First operand (number). b: Second operand (number). operation: Arithmetic operation to perform (add|subtract|multiply|divide).'
• Document output schema explicitly. Example: 'Returns {type: "object", properties: {result: {type: "number", description: "The numeric result of the operation"}, error: {type: "string", description: "Error message if operation failed"}}'
• Rename tools to follow verb_noun convention: 'add' → 'perform_addition', 'calculate' → 'perform_calculation' or 'execute_arithmetic'.
• Enhance error handling: validate inputs, return structured error objects with actionable messages (e.g., '{error: "Division by zero. Use a non-zero divisor."}'), and handle edge cases (NaN, Infinity).