Four SOAP adapter tools with consistent naming (demo_soap_*) and clear descriptions. All tools have proper JSON Schema with required parameters and type definitions. However, parameter descriptions are completely absent, the schema shows only type and required fields, with no explanation of what intA and intB represent or their valid ranges. Descriptions are adequate (50-80 chars) but lack context about when to use each tool or what the return value represents. No output schema documented. Error handling is minimal, no guidance on what happens on division by zero or invalid inputs.

• Add descriptions to intA and intB parameters in all four tools. Example: 'intA: The first integer operand (32-bit signed integer, range -2147483648 to 2147483647)' and 'intB: The second integer operand (same range; for Divide, must not be zero)'.
• Document the output schema in tool descriptions. Clarify whether the result is a plain integer or a structured response (e.g., '{"result": 42, "precision": "exact"}').
• Add error handling guidance to Divide: 'If intB is zero, returns an error. Ensure intB is not zero before calling.'
• Expand tool descriptions to include context: 'Use this to add two integers. Returns the sum. Useful for arithmetic calculations or data transformations.'
• Consider adding minimum/maximum constraints to the JSON Schema for intA and intB (e.g., 'minimum': -2147483648, 'maximum': 2147483647) to make constraints machine-parseable and prevent LLM hallucination of invalid values.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry