← AI PulseSep 21, 2026

Deep · analysis · Single-source brief

Evaluating AI Agents: From Tool Calls to Task Completion

NVIDIA details an agent evaluation framework that shifts focus from individual function calls to full task completion, using executable environments to track state across multi-step tool use.

By Illumora Editorial

Source · Sep 21, 2026, 9:05 PM · On Illumora · Sep 21, 2026, 9:12 PM

Media from the primary source — shown here so you can stay on Illumora.

Rewritten from one allowlisted primary — not independent enterprise reporting. Lanes →

Brief drafted by Illumora’s editorial model from the linked primary source. Ops desk reviews flagged pieces. How we write →

Read the source →NVIDIA Developer Blog — How to Evaluate AI Agents From Tool Calls to Task Completion | NVIDIA Technical Blog
Save

NVIDIA's Developer Blog has outlined an evolved approach to evaluating AI agents, emphasizing the execution of work chains across sequential tool calls in live environments. This framework addresses the need to measure an agent's ability to complete tasks and recover from failures, moving beyond the assessment of single function calls.

Key Points

  • Agent evaluation has evolved from scoring individual function calls to measuring full task completion.
  • Full agentic evaluation requires an execution environment that runs each tool call, tracks state, and verifies task completion.
  • Two scoring layers operate on the execution trace: step-level process scoring and end-to-end (E2E) outcome scoring.
  • Step-level scoring identifies where chains break, aiding debugging and fine-tuning efforts.
  • E2E scoring verifies if the final environment state matches the goal, reflecting the user experience.
  • Core metrics roll up through a fixed hierarchy: Benchmark → Trial → Task → Turn → Step.
  • Key metrics include accuracy, verbosity, and cost, with paired reporting such as success rate with consistency ranges.
  • Nemotron 3.5 Lightning achieved 86% accuracy on PinchBench and completed tasks 30% faster than comparable models using this framework.

Context

According to NVIDIA, early evaluation harnesses were built for static tasks, and even the Berkeley Function-Calling Leaderboard (BFCL) primarily assessed function selection and argument accuracy for individual calls. This proved insufficient for agents that operate across multi-step tasks, calling tools, handling errors, and observing results. The new approach necessitates a full execution environment that can execute each tool call, track state across steps, and read the world afterward to determine if the work was completed. A trace, which is an ordered log of an attempt including user messages, steps, and environment state, is used for both process and E2E scoring. Process scoring grades the individual steps, while E2E scoring grades the final state.

Why It Matters

This evaluation shift provides builders with a more realistic and comprehensive understanding of agent performance, moving beyond isolated call accuracy to assess an agent's ability to achieve real-world objectives. This helps ensure that deployed agents are robust and reliable in complex, dynamic environments.

What To Do

  • Review the reproducibility documentation to understand published benchmark configurations.
  • Try Nemotron 3.5 Lightning on build.nvidia.com for hands-on evaluation.
  • Consult the NIM guide to deploy Nemotron 3.5 Lightning in production.
  • Prioritize domain-specific evaluations built from real tickets and APIs for enterprise deployments.

Keep Exploring

/atlas/llama-open /atlas/claude-family /atlas/gpt-family