Two tools with basic schemas and minimal descriptions. Both tools have proper input schemas with typed parameters and enums (calculate tool), but descriptions are extremely short (10-40 chars) and lack context for LLM selection. No output schema documentation. Error handling present in calculate (divide-by-zero) but not generalized. Tool names are action verbs but lack specificity, 'add' and 'calculate' don't distinguish use cases. No parameter descriptions beyond type hints. Schemas visible and valid, but descriptions fall well below the 50-200 char baseline for A+ tools.

• Expand tool descriptions to 50-200 chars. Example: 'add: Adds two numbers and returns the sum. Use when you need basic arithmetic addition. Parameters: a (first number), b (second number). Returns: sum as a number.'
• Add descriptions to all parameters in the schema. For 'operation' enum, document: 'The arithmetic operation to perform: add (a+b), subtract (a-b), multiply (a*b), divide (a/b, returns error if b=0).'
• Document output schema explicitly. E.g., 'Returns: {type: "text", content: string representing the numeric result}'
• Rename 'add' to 'add_numbers' and 'calculate' to 'calculate_arithmetic' for clarity and to follow verb_noun convention.
• Enhance error handling with structured error responses and recovery hints. E.g., 'Division by zero: b cannot be 0. Retry with a non-zero divisor.'