A pricing agent occasionally forwards malformed tool payloads (missing currency, negative quantities) into the quote composer agent, causing bad customer quotes. What control should you add in the tool ecosystem?
Select an answer to reveal the explanation.
Short Explanation
You can’t let bad tool payloads poison the quote composer. Add schema and range checks with reject-or-repair paths before results hit shared state. That’s how you catch missing currency and negative quantities at the boundary.
Full Explanation
Implementing tool result validation and quality checks prevents malformed or nonsensical tool outputs from propagating across agents. Schema validation, business range checks, and reject or repair paths protect shared state and downstream composers.
The max token increase is wrong because token limits do not enforce payload structure or business rules.
Trusting all tool outputs because MCP guarantees semantic correctness is wrong because protocols deliver structure and transport; they do not guarantee domain correctness.
Disabling the quote composer and emailing raw tool dumps to customers is wrong because customer-facing raw dumps are unsafe and unprofessional.
Exam caveat: Validate tool outputs at the boundary before multi-agent state commits.