This server defines 12 basic arithmetic tools with minimal descriptions and no parameter-level documentation. All tools have identical structure (two float inputs, dict output) but lack depth. Descriptions are terse (10-30 chars), well below the 194-char baseline for production tools. No output schemas documented. No error handling guidance. Tools are READ_ONLY but lack explicit idempotentHint annotations. Duplicate tool sets (sumar/sumar_tool, etc.) suggest incomplete refactoring. No tool composition or chaining support.

• Expand each tool description to 100-200 chars. Example: 'Suma dos números y retorna el resultado. Útil para cálculos aritméticos básicos. Retorna un objeto con los operandos, la operación, y el resultado.'
• Document output schema explicitly in tool descriptions or via a separate schema field. Specify that all tools return {a: number, b: number, operacion: string, resultado: number} or {error: string}.
• Remove duplicate tools (sumar_tool, restar_tool, etc.). Keep only the main.py set or consolidate into a single canonical implementation.
• Add structured error responses with recovery hints. Instead of returning {error: 'No se puede dividir por cero'}, return {error: 'Division by zero', code: 'DIVISION_BY_ZERO', hint: 'Ensure divisor (b) is non-zero.'}
• Add tool annotations to all tools: mark as idempotent and read-only so LLMs know they are safe to retry and do not modify state.