Two tools with basic schemas and minimal descriptions. Both tools have input schemas with typed parameters and enums (good), but descriptions are extremely short (10-40 chars), falling well below the 50-200 char baseline for LLM-optimized descriptions. No output schema documentation. No error handling guidance. Tool names lack action verbs ('add', 'calculate' are weak; 'perform_addition', 'execute_calculation' would be clearer). No parameter descriptions beyond type info. Divide-by-zero handling exists but error message is unstructured text, not actionable guidance.

• Expand tool descriptions to 50-200 chars. Example: 'add' → 'Adds two numbers and returns the sum. Use when you need basic arithmetic addition. Returns a single numeric result.'
• Add descriptions to all parameters. Example: 'a: The first operand (any real number)', 'b: The second operand (any real number)', 'operation: The arithmetic operation to perform (add, subtract, multiply, or divide)'.
• Document output schema explicitly. Both tools return {content: [{type: 'text', text: string}]} where text is the numeric result as a string.
• Rename tools with clearer action verbs: 'add' → 'perform_addition', 'calculate' → 'execute_arithmetic_operation'. This helps LLMs distinguish intent.
• Improve error handling for divide-by-zero: return structured error like {content: [{type: 'text', text: 'Error: division by zero. Use a non-zero divisor.'}]} with actionable guidance.