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-50 chars) and lack context for LLM selection. No output schema documentation. No error handling guidance beyond a single divide-by-zero check. Tool names are verb-noun but generic ('add', 'calculate'). Parameters lack detailed constraints or format guidance. No idempotency hints, no permission declarations, no audit trail guidance.

• Expand tool descriptions to 50-200 chars. Example for 'add': 'Adds two numbers and returns the sum. Use this for simple arithmetic. Returns a single numeric result as text.'
• Document output schema explicitly. Specify that both tools return {content: [{type: 'text', text: string}]} and clarify the numeric result is returned as a string.
• Add detailed parameter descriptions with format/range hints. E.g., 'a: First number to add (any real number, including negative and decimal values)' and 'operation: The arithmetic operation to perform (add, subtract, multiply, or divide)'.
• Enhance error handling for calculate: validate inputs (reject NaN, Infinity), return actionable error messages like 'Error: Cannot divide by zero. Try a non-zero divisor.' instead of plain text.
• Add tool annotations to schema: mark both tools with readOnlyHint=true and idempotentHint=true so LLMs know they are safe to retry and do not modify state.