Two tools with basic schemas and minimal descriptions. Both tools have input schemas with proper types (number, string, enum), but descriptions are extremely brief (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' returns plain text, not structured guidance). Tool names lack action verbs ('add' and 'calculate' are weak; 'perform_addition' and 'perform_calculation' would be clearer). No parameter descriptions beyond type hints. Schemas are visible and properly typed, preventing a lower score, but the overall quality is mediocre.

• Expand tool descriptions to 50-200 chars. Example for 'add': 'Adds two numbers and returns the sum. Use this for simple two-operand addition. Returns a numeric result as text.'
• Add descriptions to all parameters. 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. Example: 'Returns an object with a single field: result (number), the computed value, or an error message if the operation fails.'
• Rename tools with clearer action verbs: 'add' → 'perform_addition', 'calculate' → 'perform_arithmetic_operation'.
• Improve error handling for divide-by-zero: return structured JSON like {error: 'division_by_zero', message: 'Cannot divide by zero. Check the divisor (b parameter) and retry.'} instead of plain text.