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), falling well below the 50-200 char baseline for LLM-optimized descriptions. No output schemas documented. Error handling is minimal (divide-by-zero check in 'calculate' only). Tool names lack action verbs ('add' and 'calculate' are weak; 'perform_addition' and 'perform_calculation' would be clearer). No parameter descriptions beyond type hints. No composition guidance or chaining metadata.

• Expand tool descriptions to 50-200 chars. Example for 'add': 'Adds two numbers and returns the sum. Use this for simple arithmetic operations. Returns a numeric result as text.'
• Rename tools with action verbs: 'add' → 'perform_addition', 'calculate' → 'perform_arithmetic_operation'.
• Add parameter descriptions: 'a' → 'First operand (any real number)', 'b' → 'Second operand (any real number)', 'operation' → 'Arithmetic operation: add, subtract, multiply, or divide'.
• Document output schema: 'Returns an object with a single 'result' field (number) or 'error' field (string) on failure.'
• Add input validation and error guidance: 'If operation is divide and b=0, return error message: "Cannot divide by zero. Provide a non-zero divisor."'