Question 640
An agent's tool-call success rate falls after a tool schema revision, but text-quality monitoring remains stable. What additional signal matters?
Explanation
Correct Answer
Agent functionality depends on external actions as well as prose generation, so tool outcomes require separate monitoring.
Incorrect Answers
Track response quality with prompt, model, and knowledge-index version labels. It addresses another case: An operator sees declining response relevance after a policy-document update but cannot distinguish which release caused it. For that case, the distinguishing justification or acceptance check is: Version-aware dashboards correlate performance changes with the exact dependencies deployed at each interval. The present case instead states: An agent's tool-call success rate falls after a tool schema revision, but text-quality monitoring remains stable. It calls for Monitor agent tool execution quality and failure rates independently. Showing success for the other case would not establish: Agent functionality depends on external actions as well as prose generation, so tool outcomes require separate monitoring.
The alternative, Apply approved redaction, access controls, and retention limits to monitoring data, belongs to a different technical condition: A monitoring process keeps every raw conversation indefinitely, contrary to retention policy. There the source-specific mechanism or proof is: Observability must not create an uncontrolled second store of sensitive customer conversations. The condition asked about here is: An agent's tool-call success rate falls after a tool schema revision, but text-quality monitoring remains stable. A suitable correction is Monitor agent tool execution quality and failure rates independently; the targeted justification or result is: Agent functionality depends on external actions as well as prose generation, so tool outcomes require separate monitoring.
Attach actionable alert thresholds and operational notification routes to critical monitoring signals. That operation would be relevant if: An application has live quality dashboards but no paging when a critical policy failure occurs. Its corresponding reason or verification is: Dashboards alone require manual inspection; alerting ensures serious failures reach responders promptly. However the problem in this question is: An agent's tool-call success rate falls after a tool schema revision, but text-quality monitoring remains stable. The requirement instead calls for Monitor agent tool execution quality and failure rates independently; the question-specific check is: Agent functionality depends on external actions as well as prose generation, so tool outcomes require separate monitoring.