Two tools with basic schemas and minimal descriptions. Both tools have proper input schemas with typed parameters and enums (calculate tool), but descriptions are extremely short (10-40 chars, well below the 50-200 char baseline for LLM-optimized descriptions). No output schema documentation. Error handling is minimal (divide-by-zero check in calculate tool 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 for 'add': 'Adds two numbers and returns the sum. Use this for simple two-operand addition. Returns a numeric result as text.'
• Add descriptions to all parameters. Example: 'a: The first number to add (any real number)' and 'b: The second number to add (any real number)'. For 'operation' in calculate: 'The arithmetic operation to perform: add, subtract, multiply, or divide.'
• Document output schema explicitly. Example: 'Returns an object with a single text field containing the numeric result as a string. Example: {content: [{type: "text", text: "42"}]}'
• Rename tools with action verbs: 'add' → 'perform_addition', 'calculate' → 'perform_arithmetic_operation'. This makes intent clear from the name alone.
• Add validation and error guidance. For 'add': validate that inputs are numbers; return 'Invalid input: a and b must be numbers.' For 'calculate': return 'Invalid operation: must be one of [add, subtract, multiply, divide].' Include recovery hints.