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), 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' only). Tool names lack action verbs ('add', 'calculate' are weak; 'perform_addition', 'execute_calculation' would be clearer). Parameters lack detailed descriptions explaining constraints, ranges, or use cases. No documentation of what the tools return or when to use one vs. the other.

• Expand tool descriptions to 50-200 chars. Example: 'add' → 'Adds two numbers and returns the sum. Use for simple arithmetic operations. Accepts integers and decimals. Returns result as a number.'
• Rename tools with action verbs: 'add' → 'perform_addition', 'calculate' → 'execute_arithmetic'. This helps LLMs disambiguate intent from the name alone.
• Add parameter descriptions explaining constraints and use cases. Example: 'a: First operand (integer or decimal, no limit). b: Second operand (integer or decimal, no limit).'
• Document output schema explicitly. Example: 'Returns {result: number, operation: string, timestamp: ISO8601}' so LLMs know what fields to expect.
• Add comprehensive error handling with recovery guidance. Example: 'Invalid operation. Must be one of: add, subtract, multiply, divide. Retry with a valid operation.'