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-50 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_calculation). No parameter descriptions beyond type hints. Schemas are present but descriptions fall well below the 194-char baseline for production tools.

• Expand tool descriptions to 100-200 chars. Example for 'add': 'Adds two numbers and returns their sum. Use this for simple arithmetic when you need to combine numeric values. Returns a single numeric result.'
• Rename tools with action verbs: 'add' → 'compute_sum', 'calculate' → 'perform_arithmetic'. This helps LLMs disambiguate intent.
• Add descriptions to all parameters. Example: 'a: First operand (numeric value to add)', 'b: Second operand (numeric value to add)', 'operation: Arithmetic operation to perform (add, subtract, multiply, or divide)'.
• Document output schema explicitly. Example: 'Returns an object with a single field: result (number), the computed value.'
• Enhance error handling with actionable messages. For divide-by-zero, return structured error: {error: 'Division by zero', suggestion: 'Provide a non-zero divisor'}. For invalid operations, list valid options.