Editorial illustration for New Architecture Separates Execution and Review Agents for Tool-Calling
New Architecture Separates Execution and Review Agents...
When an AI agent calls a tool, who watches the watcher? The answer, it turns out, is another agent, but that fixer can break things too. This new architecture splits the work: one agent executes, a second reviews.
The tradeoff is real, and until now, unmeasured. Enter Helpfulness-Harmfulness metrics, a direct way to see if the reviewer is actually helping or just adding noise. Across single-turn and multi-turn benchmarks, the results speak for themselves.
In practice, this architecture establishes a clear separation of concerns between the primary execution agent and a secondary review agent. As with any multi-agent system, the reviewer can introduce new errors while correcting others, yet no prior work to our knowledge has systematically measured this tradeoff. To quantify this tradeoff, we introduce Helpfulness-Harmfulness metrics: helpfulness measures the percentage of base agent errors that feedback corrects; harmfulness measures the percentage of correct responses that feedback degrades.
These metrics directly inform reviewer design by revealing whether a given model or prompt provides net positive value. We evaluate our approach on BFCL (single-turn) and Ï2-Bench (multi-turn stateful scenarios), achieving +5.5% on irrelevance detection and +7.1% on multi-turn tasks.
A tradeoff measured is a tradeoff mastered. The Helpfulness-Harmfulness framework doesn’t just quantify the double-edged nature of reviewer feedback, it flips it into a design lever. Apple’s architecture proves that separating execution from review isn’t mere engineering neatness; it’s a strategic win.
Gains of 5.5% in irrelevance detection and 7.1% on multi-turn tasks are not trivial. They signal a shift: the question is no longer whether to add a reviewer, but how to tune one that adds more than it subtracts. That precise calibration is now possible.
The rest of the field should take note.
Common Questions Answered
How does the dual-agent architecture separate execution and review in tool-calling?
The architecture splits responsibilities between two agents: one agent executes the tool calls while a second agent reviews the execution for potential issues. This separation allows for independent evaluation of actions, though the review process itself can introduce new problems that need to be measured and managed.
What are Helpfulness-Harmfulness metrics and why are they important?
Helpfulness-Harmfulness metrics provide a direct measurement framework to determine whether a reviewer agent is actually improving outcomes or simply adding noise to the system. These metrics are crucial because they quantify the tradeoff between having a reviewer and the potential risks it introduces, enabling data-driven design decisions.
What performance improvements does Apple's architecture achieve on multi-turn tasks?
Apple's dual-agent architecture demonstrates a 7.1% improvement on multi-turn tasks and a 5.5% gain in irrelevance detection across benchmarks. These gains indicate that properly tuned reviewer agents provide significant strategic advantages beyond mere engineering optimization.
How does measuring tradeoffs change the approach to adding reviewer agents?
By measuring tradeoffs through the Helpfulness-Harmfulness framework, the question shifts from whether to add a reviewer agent to how to optimally tune one that maximizes benefits. This measurement-driven approach transforms reviewer feedback into a strategic design lever rather than a binary decision.