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' returns text, not structured error). Tool names lack action verbs ('add' and 'calculate' are weak; 'perform_addition' and 'perform_calculation' would be clearer). No parameter descriptions beyond type hints. No tool annotations (readOnlyHint, idempotentHint). Composition is reasonable (two separate tools), but descriptions do not guide LLM selection or explain when to use each.

• Expand tool descriptions to 50-200 chars. Example: 'add' → 'Add two numbers and return their sum. Use when you need basic arithmetic addition. Returns a single numeric result.'
• Add descriptions to all parameters. Example: 'a: The first number to add (any real number)', 'b: The second number to add (any real number)'.
• Document output schema in tool description or via a separate schema field. Example: 'Returns {content: [{type: "text", text: string}]} where text is the numeric result as a string.'
• Rename tools with clearer action verbs: 'add' → 'perform_addition', 'calculate' → 'perform_arithmetic' or 'compute_operation'.
• Improve error handling in 'calculate': return structured error like {error: 'division_by_zero', message: 'Cannot divide by zero. Check that b is non-zero and retry.'} instead of plain text.