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, compute_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' → 'Add two numbers and return their sum. Accepts integers and decimals. Use this for simple addition; use calculate for subtract, multiply, or divide.'
• Rename tools with action verbs: 'add' → 'compute_sum', 'calculate' → 'compute_arithmetic'. This helps LLMs disambiguate and parse intent from the name.
• Add parameter descriptions in schema. Example: 'a: {type: number, description: "First operand (integer or decimal, no bounds)"}' and 'operation: {type: string, enum: [...], description: "Arithmetic operation: add, subtract, multiply, or divide"}'.
• Document output schema. Declare that both tools return {type: 'text', text: string} containing the numeric result or error message.
• Enhance error messages. Instead of 'Error: Cannot divide by zero', return 'Error: Division by zero. Divisor (b) must be non-zero. Please provide a non-zero value for b.'