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) and lack context for LLM selection. No output schema documentation. Error handling is minimal (divide-by-zero check in calculate tool only). Tool names lack action verbs (add, calculate are weak; should be compute_sum, perform_arithmetic). No parameter descriptions beyond type hints. Schemas are present but descriptions fall well below the 50-200 char baseline for A-grade 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: numeric sum.'
• Rename tools with action verbs: 'add' → 'compute_sum', 'calculate' → 'perform_arithmetic_operation'. This signals intent and helps LLMs disambiguate.
• Add descriptions to all parameters. Example for calculate: operation='The arithmetic operation to perform (add, subtract, multiply, divide)', a='First operand (any number)', b='Second operand (any number)'.
• Document output schema explicitly. Declare that both tools return {type: 'text', text: string} and specify the format of the text (e.g., 'numeric result as a string' or 'error message').
• Enhance error handling in add tool (validate inputs are numbers) and improve error messages in calculate to include the constraint violated (e.g., 'Cannot divide by zero. Ensure b ≠ 0.').