A travel multi-agent app calls a flaky third-party fare API. Intermittent 429 and 503 responses currently cause the planner to invent prices. You must harden tool use. What should you implement?
Select an answer to reveal the explanation.
Short Explanation
Correct answer: C. Tool error-handling, fallbacks, and result validation are required development skills. Fabricating prices (A) is dangerous. Hard process crashes (B) hurt reliability. Hiding errors (D) blocks recovery. Propagate structured failures, retry transient faults, and fall back safely with user-visible degradation when needed.
Full Explanation
Production multi-agent systems must assume tools fail. Implement retries/backoff for 429/5xx, circuit breakers for prolonged outages, secondary data sources or degraded modes, and clear error objects the orchestrator can branch on (retry, ask user, cancel). Result validation and quality checks prevent the model from treating missing data as license to hallucinate. Option A creates business and trust risk. Option B worsens availability. Option D removes signal required for control flow. Log tool failures with correlation IDs and include them in reliability monitors.