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 are action-oriented (add, calculate) but lack verb_noun clarity. No parameter descriptions beyond type hints. No composition guidance or chaining IDs. Schemas are present but sparse.

• Expand tool descriptions to 50-200 chars. Example: 'add' → 'Add two numbers and return their sum. Use when you need basic arithmetic addition. Returns the numeric result as text.'
• Add parameter descriptions. For 'a' and 'b': 'First/second operand (numeric value, any range)'. For 'operation': 'Arithmetic operation to perform: add, subtract, multiply, or divide.'
• Document output schema in tool description: 'Returns {content: [{type: "text", text: "<numeric result>"}]}'.
• Enhance error handling: catch invalid inputs (non-numeric 'a'/'b'), return actionable errors like 'Invalid input: a must be a number, got <value>'. Add timeout guards for long-running operations.
• Rename 'calculate' to 'perform_arithmetic' or split into separate tools (add_numbers, subtract_numbers, multiply_numbers, divide_numbers) to avoid overlap with 'add' and improve LLM disambiguation.