Two tools with basic schemas and minimal descriptions. Both tools have input schemas with proper types (number, enum), but descriptions are extremely short (18-47 chars, well below the 50-200 char baseline for LLM-optimized descriptions). The 'calculate' tool has a proper enum constraint for operations, but neither tool documents output structure, error recovery paths, or when to use one vs. the other. No parameter descriptions beyond the schema. Error handling exists (divide-by-zero check) but returns unstructured text rather than actionable guidance.

• Expand tool descriptions to 80-150 chars. Example for 'add': 'Adds two numbers and returns their sum. Use this for simple two-operand addition. For multi-operation arithmetic (subtract, multiply, divide), use the calculate tool instead.'
• Add parameter descriptions to all inputs. Example: 'a: First number to add (any real number)', 'b: Second number to add (any real number)', 'operation: Arithmetic operation to perform (add, subtract, multiply, or divide)'.
• Document output schema explicitly. Example: 'Returns {content: [{type: "text", text: "<numeric result as string>"}]}'. Specify that results are returned as text strings, not numbers.
• Enhance error handling with actionable messages. For divide-by-zero: 'Cannot divide by zero. Check your inputs: a=<value>, b=<value>. Ensure the divisor (b) is non-zero.' Include the invalid values and the constraint violated.
• Rename tools for clarity: 'add' → 'add_numbers', 'calculate' → 'perform_arithmetic'. Add a discovery note in descriptions: 'For simple addition of two numbers, use add_numbers. For subtract, multiply, or divide, use perform_arithmetic.'