Two tools with basic schemas and minimal descriptions. Both tools have input schemas with proper types (number, string enum), but descriptions are extremely brief (10-15 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' and 'calculate' are weak; 'perform_addition' and 'perform_calculation' would be clearer). No parameter descriptions beyond type info. No guidance on when to use one tool vs. the other.

• Expand tool descriptions to 50-200 chars. Example: 'add' → 'Adds two numbers and returns the sum. Use when you need basic arithmetic addition. Returns a single numeric result.'
• Add descriptions to all parameters. Example: 'a: First number to add (any real number)', 'b: Second number to add (any real number)', 'operation: The arithmetic operation to perform (add, subtract, multiply, or divide)'.
• Document output schema explicitly. Specify that both tools return {type: 'text', text: string} and clarify the format of the numeric result (e.g., 'floating-point number as a string').
• Rename tools with action verbs: 'add' → 'perform_addition', 'calculate' → 'perform_arithmetic'. This clarifies intent and helps LLMs distinguish between them.
• Add error handling guidance. For divide-by-zero, return a structured error like {type: 'error', message: 'Cannot divide by zero. Check your inputs and try again.'} instead of plain text.