A Fulfilment agent calls a warehouse inventory tool. Intermittent 503 responses and occasional schema-mismatched payloads cause the agent to invent stock levels and continue the workflow. You must implement robust tool integration behavior. What combination should you design?
Select an answer to reveal the explanation.
Short Explanation
You need to classify tool failures, retry transient 503s with backoff, fall back to a cached snapshot or human escalation, and validate payloads before reasoning. That stops invented stock levels and keeps the workflow honest. Fake defaults, no error handling, and tight infinite retries all make things worse.
Full Explanation
Develop-domain guidance calls for tool error-handling and fallback mechanisms plus tool result validation and quality checks. The correct design classifies tool failures, retries transient 503s with backoff, uses a fallback path such as a cached snapshot or human escalation when retries exhaust, and validates payloads against a schema before the agent reasons over them. That prevents invented stock levels after 503s or malformed responses. Silently substituting a confident-sounding default quantity of 999 units on any tool error is wrong because fabricated defaults create incorrect fulfilment decisions and hide outages. Removing error handling so the agent's natural language improvisation can resolve outages is wrong because unhandled tool failures commonly drive model hallucination rather than recovery. Retrying the same failing call in a tight infinite loop with no backoff until the process is killed is wrong because infinite tight retries harm downstream systems and do not guarantee recovery. Exam tip: Retry + backoff + fallback + schema validation before the agent continues.