A travel multi-agent solution calls an airline inventory tool. Intermittent 503s and schema validation failures occur. Which tool error-handling and fallback design should you implement?
Select an answer to reveal the explanation.
Short Explanation
Treat tools like distributed dependencies. Transient 503s get bounded retries with backoff; bad payloads fail schema validation; persistent failure falls back to another tool or a graceful “availability uncertain” path — not invented flights. Option C. Infinite retry (A) hangs the system. Fabrication (B) is unsafe. Shutting the product down forever (D) is not a fallback strategy.
Full Explanation
Building tool ecosystems includes error-handling, fallback mechanisms, and result validation. Option C combines transient fault handling, quality checks, and controlled degradation.
Option A risks cascading latency and resource exhaustion.
Option B produces incorrect bookings and destroys trust.
Option D confuses a single fault with total system retirement.
Patterns: classify errors (transient vs permanent), circuit-break unhealthy tools, and notify the orchestrator so it can replan.
Exam tip: Never “hallucinate tool success” when the tool failed.