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. Error handling is minimal (divide-by-zero check in calculate tool only). Tool names lack action verbs (add, calculate are weak; should be compute_sum, perform_arithmetic). No parameter descriptions beyond type hints. Schemas use Zod validation but lack JSON Schema documentation visible to clients.

• Expand tool descriptions to 50-200 chars. Example: 'add' → 'Adds two numbers and returns the sum. Use when you need basic arithmetic addition. Parameters: a (first number), b (second number). Returns: numeric sum.'
• Rename tools with action verbs: 'add' → 'compute_sum', 'calculate' → 'perform_arithmetic'. This follows verb_noun convention and helps LLMs parse intent.
• Add descriptions to all parameters in the schema. For 'operation' enum, document: 'The arithmetic operation to perform. Must be one of: add, subtract, multiply, divide.'
• Document output schema explicitly. Publish that both tools return {type: 'text', text: string} and specify the format of the numeric result (e.g., 'floating-point number as string').
• Enhance error handling with actionable messages. For invalid operation, return: 'Invalid operation: got "modulo", must be one of: add, subtract, multiply, divide.' For divide-by-zero, suggest: 'Cannot divide by zero. Check your inputs and retry.'