Tool Use

Q: How do I check whether my agent called the right tools across a conversation?

ToolUseMetric evaluates each interaction's tool selection and then the arguments passed, flagging both wrong-tool turns and right-tool-but-wrong-arguments turns.

Q: Why do I have to pass available tools if the agent already called tools?

is the full menu of ToolCalls the agent could have used. Without the alternatives, the metric can't tell whether a better tool existed or whether a tool should have been called at all.

Q: My agent picked the right tool but with wrong arguments — does that fail?

Yes. The final score is min(ToolSelectionScore, ArgumentCorrectnessScore), so a perfect tool choice with bad arguments still drags it down. The argument score only applies to turns where a tool was called.

Q: Does it catch unnecessary or missing tool calls?

Both hurt the Tool Selection Score: calling an unneeded tool or skipping a needed one scores as poor selection against . Use for per-interaction reasoning.

LLM-as-a-judge

Multi-turn

Referenceless

Agent

Multimodal

The Tool Use metric is a multi-turn agentic metric that evaluates your LLM agent's tool selection and argument generation capabilities. It is a self-explaining eval, which means it outputs a reason for its metric score.

Required Arguments

To use the ToolUseMetric, you'll have to provide the following arguments when creating a ConversationalTestCase:

turns

You can learn more about how it is calculated here.

Usage

The ToolUseMetric() can be used for end-to-end multi-turn evaluations of agents.

from deepeval.test_case import Turn, ConversationalTestCase, ToolCall
from deepeval.metrics import ToolUseMetric
from deepeval import evaluate

convo_test_case = ConversationalTestCase(
    turns=[
        Turn(role="...", content="..."), 
        Turn(role="...", content="...", tools_called=[...])
    ],
)
metric = ToolUseMetric(threshold=0.5)

# To run metric as a standalone
# metric.measure(convo_test_case)
# print(metric.score, metric.reason)

evaluate(test_cases=[convo_test_case], metrics=[metric])

There is ONE mandatory and SEVEN optional parameters when creating a ToolUseMetric:

available_tools: a list of ToolCalls that give context on all the tools that were available to your LLM agent. This list is used to evaluate your agent's tool selection capability.
[Optional] threshold: a number representing the minimum passing threshold. Can also be set to None to run the metric in score-only mode. Defaulted to 0.5.
[Optional] model: a string specifying which of OpenAI's GPT models to use, OR any custom LLM model of type DeepEvalBaseLLM. Defaulted to gpt-5.4.
[Optional] include_reason: a boolean which when set to True, will include a reason for its evaluation score. Defaulted to True.
[Optional] strict_mode: a boolean which when set to True, enforces a binary metric score: 1 for perfection, 0 otherwise. It also overrides the current threshold and sets it to 1. Defaulted to False.
[Optional] async_mode: a boolean which when set to True, enables concurrent execution within the measure() method. Defaulted to True.
[Optional] verbose_mode: a boolean which when set to True, prints the intermediate steps used to calculate said metric to the console, as outlined in the How Is It Calculated section. Defaulted to False.
[Optional] flaky: a boolean which when set to True, marks the metric as flaky. Defaulted to False.

As a standalone

You can also run the ToolUseMetric on a single test case as a standalone, one-off execution.

...

metric.measure(convo_test_case)
print(metric.score, metric.reason)

How Is It Calculated

The ToolUseMetric score is determined through the following process:

Compute the Tool Selection Score for each unit interaction.
Compute the Argument Correctness Score for all unit interactions that include tool calls.

\text{Tool Use Score} = \min(\text{ToolSelectionScore}, \text{ArgumentCorrectnessScore})

The Tool Selection Score evaluates whether the agent chose the most appropriate tool for the task among all the available tools.
The Argument Correctness Score assesses whether the arguments provided in the tool call were accurate and suitable for the task. This score is only considered when a tool call has been made.

FAQs

How do I check whether my agent called the right tools across a conversation?

ToolUseMetric evaluates each interaction's tool selection and then the arguments passed, flagging both wrong-tool turns and right-tool-but-wrong-arguments turns.

Why do I have to pass available tools if the agent already called tools?

available_tools is the full menu of ToolCalls the agent could have used. Without the alternatives, the metric can't tell whether a better tool existed or whether a tool should have been called at all.

My agent picked the right tool but with wrong arguments — does that fail?

Yes. The final score is min(ToolSelectionScore, ArgumentCorrectnessScore), so a perfect tool choice with bad arguments still drags it down. The argument score only applies to turns where a tool was called.

Does it catch unnecessary or missing tool calls?

Both hurt the Tool Selection Score: calling an unneeded tool or skipping a needed one scores as poor selection against available_tools. Use verbose_mode for per-interaction reasoning.