Two tools with basic schemas and minimal descriptions. Both tools have input schemas with proper types (number, string enum), but descriptions are extremely short (18-45 chars, well below the 50-200 char baseline for LLM-optimized descriptions). Parameter descriptions are present but terse. No output schema documentation. Error handling exists (divide-by-zero check) but lacks recovery guidance. Tool names are action-oriented (add, calculate) but lack verb prefixes. No tool annotations (readOnlyHint, idempotentHint). Composition is reasonable, two separate tools rather than one combined tool.

• 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.' and 'calculate: Performs arithmetic operations (add, subtract, multiply, divide) on two numbers. Use for complex calculations. Returns numeric result or error message.'
• Document output schema explicitly. Specify that both tools return {content: [{type: 'text', text: string}]} and clarify the text field contains the numeric result or error message.
• Add tool annotations to schema. Mark both tools with readOnlyHint: true and idempotentHint: true so agents know they are safe to retry.
• Improve error handling for divide-by-zero. Return structured error: {content: [{type: 'text', text: 'Error: Cannot divide by zero. Divisor (b) must be non-zero.'}]} with clear constraint violation message.
• Consider renaming tools to verb_noun convention: 'perform_addition' and 'perform_calculation' for better LLM disambiguation when multiple arithmetic tools exist.