Practice vocabulary for evaluating agentic AI systems: trajectory evaluation, task completion rate, tool call accuracy, and benchmarks.
0 / 45 completed
1 / 45
A researcher says 'We use agent trajectory evaluation.' What does 'trajectory' refer to in this context?
An agent trajectory is the complete sequence of steps an agent takes — including observations, reasoning, and actions — from receiving a task to producing a final result. Evaluating the trajectory reveals whether the agent reasoned correctly, not just whether it got the right answer.
2 / 45
Your team reports 'The agent completed the task in 8 steps vs. the expected 5.' Why does step count matter in agentic evaluation?
In agentic systems, unnecessary steps add latency and cost, and each step is a point where errors can compound. Comparing actual vs. expected step counts helps evaluate agent efficiency and reasoning quality.
3 / 45
An evaluation report shows 'tool call accuracy: 78%.' What does this metric measure?
Tool call accuracy measures whether the agent selected the right tool AND supplied correct arguments. An agent might call the right tool with wrong parameters — a failure mode this metric captures.
4 / 45
A colleague mentions 'the agent's reasoning trace shows the agent misidentified the goal.' What is a reasoning trace?
A reasoning trace (also called a thought trace or chain-of-thought log) shows how the agent broke down a task, what it decided at each step, and why. It is essential for diagnosing agent failures.
5 / 45
Your team says 'We benchmark the agent on SWE-bench.' What type of benchmark is this?
SWE-bench is an agentic benchmark where agents must solve real-world software engineering tasks (GitHub issues) by writing and executing code. It is widely used to evaluate coding agents on realistic tasks.
6 / 45
PR Description
Subject: Agent Performance Update - Order Processing
Body:
Agent successfully processed 127 out of 130 orders. However, the agent exhibited a high rate of 're-routing' – specifically, 5 orders were incorrectly directed to the shipping department instead of customer support. Further investigation into the agent's decision-making process is required.
Note: Agent ID: 7492
This question tests understanding of how 're-routing' is used in agentic evaluation. It's not simply about overall success rate; it highlights a specific *deviation* from the intended process – in this case, incorrect routing. The correct answer focuses on the need to examine the agent's decision-making logic because that's where the problem lies, correcting the misconception that 'success' always equates to perfect adherence to a defined workflow.
7 / 45
Reviewer: "The agent's action log shows it repeatedly attempted to use the sendEmail function even after receiving a 'no recipient' error. This suggests a lack of robustness in its handling of API responses." What does 'action log' refer to in this context, and why is this observation significant for evaluating the agent's performance?
Action log refers to a precise record of every function call or API interaction made by the agent. This is crucial because it allows developers to understand *how* the agent attempted to solve a problem, not just the outcome. Observing repeated attempts after an error (like `sendEmail` failing) highlights a potential weakness in the agent's logic – namely, its inability to gracefully handle API errors and retry appropriately, impacting robustness.
8 / 45
**Scenario:** Your team reports 'The agent completed the task in 8 steps vs. the expected 5.'
Question: Why does step count matter in agentic evaluation?
Options:
A) Step count is irrelevant; only the outcome of the task matters. B) Step count indicates potential inefficiencies and deviations from expected behavior, providing a metric for comparison and optimization. C) Agents should always strive to complete tasks in fewer steps, regardless of context or complexity. D) Step count measures the agent's intelligence level, reflecting its ability to solve complex problems.
This question tests understanding of metrics in agentic evaluation. Option B is correct because step count provides a quantifiable measure of efficiency and potential deviations from the intended execution path. Options A, C, and D are incorrect as they focus on irrelevant factors or misinterpretations of the metric's purpose.
9 / 45
**Scenario:** A colleague mentions 'the agent's reasoning trace shows the agent misidentified the goal.'
Question: What is a reasoning trace?
Options:
A) A detailed report of the agent's financial transactions. B) A log of all commands executed by the agent, regardless of their relevance to the task. C) A record of the steps the agent took to reach its decision-making process and identify the goal. D) A summary of user feedback regarding the agent's performance.
The correct answer is C. A reasoning trace specifically documents *how* an agent arrived at a decision or goal. It's crucial for debugging and understanding the agent's thought process, not just its actions. Options A, B, and D describe different types of logs or feedback, but don't represent the core concept of a 'reasoning trace'.
10 / 45
**Scenario:** Your team says 'We benchmark the agent on SWE-bench.'
Question: What type of benchmark is this?
Options:
A) An evaluation based solely on subjective human judgment. B) A standardized test designed to measure an agent's performance against a defined set of criteria and a baseline. C) A casual observation of the agent's behavior during a typical workday. D) An analysis of the agent's code commits over the past month.
Option B is correct. SWE-bench (Software Engineering Benchmark) refers to a standardized testing framework used in agentic evaluation. These benchmarks provide objective metrics for comparing different agents and tracking performance improvements over time. Options A, C, and D are inaccurate representations of benchmarking.
11 / 45
PR Description
Subject: Agent Performance Update - Order Processing
Body:
Agent successfully processed 127 out of 130 orders. However, the agent exhibited a high rate of 're-routing' – specifically, 5 orders were incorrectly directed to the shipping department instead of customer support. Further investigation into the agent's decision-making process is required.
Note: Agent ID: 7492
This question tests understanding of how 're-routing' is used in agentic evaluation. It's not simply about overall success rate; it highlights a specific *deviation* from the intended process – in this case, incorrect routing. The correct answer focuses on the need to examine the agent's decision-making logic because that's where the problem lies, correcting the misconception that 'success' always equates to perfect adherence to a defined workflow.
12 / 45
Reviewer: "The agent's action log shows it repeatedly attempted to use the sendEmail function even after receiving a 'no recipient' error. This suggests a lack of robustness in its handling of API responses." What does 'action log' refer to in this context, and why is this observation significant for evaluating the agent's performance?
Action log refers to a precise record of every function call or API interaction made by the agent. This is crucial because it allows developers to understand *how* the agent attempted to solve a problem, not just the outcome. Observing repeated attempts after an error (like `sendEmail` failing) highlights a potential weakness in the agent's logic – namely, its inability to gracefully handle API errors and retry appropriately, impacting robustness.
13 / 45
**Scenario:** Your team reports 'The agent completed the task in 8 steps vs. the expected 5.'
Question: Why does step count matter in agentic evaluation?
Options:
A) Step count is irrelevant; only the outcome of the task matters. B) Step count indicates potential inefficiencies and deviations from expected behavior, providing a metric for comparison and optimization. C) Agents should always strive to complete tasks in fewer steps, regardless of context or complexity. D) Step count measures the agent's intelligence level, reflecting its ability to solve complex problems.
This question tests understanding of metrics in agentic evaluation. Option B is correct because step count provides a quantifiable measure of efficiency and potential deviations from the intended execution path. Options A, C, and D are incorrect as they focus on irrelevant factors or misinterpretations of the metric's purpose.
14 / 45
**Scenario:** A colleague mentions 'the agent's reasoning trace shows the agent misidentified the goal.'
Question: What is a reasoning trace?
Options:
A) A detailed report of the agent's financial transactions. B) A log of all commands executed by the agent, regardless of their relevance to the task. C) A record of the steps the agent took to reach its decision-making process and identify the goal. D) A summary of user feedback regarding the agent's performance.
The correct answer is C. A reasoning trace specifically documents *how* an agent arrived at a decision or goal. It's crucial for debugging and understanding the agent's thought process, not just its actions. Options A, B, and D describe different types of logs or feedback, but don't represent the core concept of a 'reasoning trace'.
15 / 45
**Scenario:** Your team says 'We benchmark the agent on SWE-bench.'
Question: What type of benchmark is this?
Options:
A) An evaluation based solely on subjective human judgment. B) A standardized test designed to measure an agent's performance against a defined set of criteria and a baseline. C) A casual observation of the agent's behavior during a typical workday. D) An analysis of the agent's code commits over the past month.
Option B is correct. SWE-bench (Software Engineering Benchmark) refers to a standardized testing framework used in agentic evaluation. These benchmarks provide objective metrics for comparing different agents and tracking performance improvements over time. Options A, C, and D are inaccurate representations of benchmarking.
16 / 45
PR Description
Subject: Agent Performance Update - Order Processing
Body:
Agent successfully processed 127 out of 130 orders. However, the agent exhibited a high rate of 're-routing' – specifically, 5 orders were incorrectly directed to the shipping department instead of customer support. Further investigation into the agent's decision-making process is required.
Note: Agent ID: 7492
This question tests understanding of how 're-routing' is used in agentic evaluation. It's not simply about overall success rate; it highlights a specific *deviation* from the intended process – in this case, incorrect routing. The correct answer focuses on the need to examine the agent's decision-making logic because that's where the problem lies, correcting the misconception that 'success' always equates to perfect adherence to a defined workflow.
17 / 45
Reviewer: "The agent's action log shows it repeatedly attempted to use the sendEmail function even after receiving a 'no recipient' error. This suggests a lack of robustness in its handling of API responses." What does 'action log' refer to in this context, and why is this observation significant for evaluating the agent's performance?
Action log refers to a precise record of every function call or API interaction made by the agent. This is crucial because it allows developers to understand *how* the agent attempted to solve a problem, not just the outcome. Observing repeated attempts after an error (like `sendEmail` failing) highlights a potential weakness in the agent's logic – namely, its inability to gracefully handle API errors and retry appropriately, impacting robustness.
18 / 45
**Scenario:** Your team reports 'The agent completed the task in 8 steps vs. the expected 5.'
Question: Why does step count matter in agentic evaluation?
Options:
A) Step count is irrelevant; only the outcome of the task matters. B) Step count indicates potential inefficiencies and deviations from expected behavior, providing a metric for comparison and optimization. C) Agents should always strive to complete tasks in fewer steps, regardless of context or complexity. D) Step count measures the agent's intelligence level, reflecting its ability to solve complex problems.
This question tests understanding of metrics in agentic evaluation. Option B is correct because step count provides a quantifiable measure of efficiency and potential deviations from the intended execution path. Options A, C, and D are incorrect as they focus on irrelevant factors or misinterpretations of the metric's purpose.
19 / 45
**Scenario:** A colleague mentions 'the agent's reasoning trace shows the agent misidentified the goal.'
Question: What is a reasoning trace?
Options:
A) A detailed report of the agent's financial transactions. B) A log of all commands executed by the agent, regardless of their relevance to the task. C) A record of the steps the agent took to reach its decision-making process and identify the goal. D) A summary of user feedback regarding the agent's performance.
The correct answer is C. A reasoning trace specifically documents *how* an agent arrived at a decision or goal. It's crucial for debugging and understanding the agent's thought process, not just its actions. Options A, B, and D describe different types of logs or feedback, but don't represent the core concept of a 'reasoning trace'.
20 / 45
**Scenario:** Your team says 'We benchmark the agent on SWE-bench.'
Question: What type of benchmark is this?
Options:
A) An evaluation based solely on subjective human judgment. B) A standardized test designed to measure an agent's performance against a defined set of criteria and a baseline. C) A casual observation of the agent's behavior during a typical workday. D) An analysis of the agent's code commits over the past month.
Option B is correct. SWE-bench (Software Engineering Benchmark) refers to a standardized testing framework used in agentic evaluation. These benchmarks provide objective metrics for comparing different agents and tracking performance improvements over time. Options A, C, and D are inaccurate representations of benchmarking.
21 / 45
PR Description
Subject: Agent Performance Update - Order Processing
Body:
Agent successfully processed 127 out of 130 orders. However, the agent exhibited a high rate of 're-routing' – specifically, 5 orders were incorrectly directed to the shipping department instead of customer support. Further investigation into the agent's decision-making process is required.
Note: Agent ID: 7492
This question tests understanding of how 're-routing' is used in agentic evaluation. It's not simply about overall success rate; it highlights a specific *deviation* from the intended process – in this case, incorrect routing. The correct answer focuses on the need to examine the agent's decision-making logic because that's where the problem lies, correcting the misconception that 'success' always equates to perfect adherence to a defined workflow.
22 / 45
Reviewer: "The agent's action log shows it repeatedly attempted to use the sendEmail function even after receiving a 'no recipient' error. This suggests a lack of robustness in its handling of API responses." What does 'action log' refer to in this context, and why is this observation significant for evaluating the agent's performance?
Action log refers to a precise record of every function call or API interaction made by the agent. This is crucial because it allows developers to understand *how* the agent attempted to solve a problem, not just the outcome. Observing repeated attempts after an error (like `sendEmail` failing) highlights a potential weakness in the agent's logic – namely, its inability to gracefully handle API errors and retry appropriately, impacting robustness.
23 / 45
**Scenario:** Your team reports 'The agent completed the task in 8 steps vs. the expected 5.'
Question: Why does step count matter in agentic evaluation?
Options:
A) Step count is irrelevant; only the outcome of the task matters. B) Step count indicates potential inefficiencies and deviations from expected behavior, providing a metric for comparison and optimization. C) Agents should always strive to complete tasks in fewer steps, regardless of context or complexity. D) Step count measures the agent's intelligence level, reflecting its ability to solve complex problems.
This question tests understanding of metrics in agentic evaluation. Option B is correct because step count provides a quantifiable measure of efficiency and potential deviations from the intended execution path. Options A, C, and D are incorrect as they focus on irrelevant factors or misinterpretations of the metric's purpose.
24 / 45
**Scenario:** A colleague mentions 'the agent's reasoning trace shows the agent misidentified the goal.'
Question: What is a reasoning trace?
Options:
A) A detailed report of the agent's financial transactions. B) A log of all commands executed by the agent, regardless of their relevance to the task. C) A record of the steps the agent took to reach its decision-making process and identify the goal. D) A summary of user feedback regarding the agent's performance.
The correct answer is C. A reasoning trace specifically documents *how* an agent arrived at a decision or goal. It's crucial for debugging and understanding the agent's thought process, not just its actions. Options A, B, and D describe different types of logs or feedback, but don't represent the core concept of a 'reasoning trace'.
25 / 45
**Scenario:** Your team says 'We benchmark the agent on SWE-bench.'
Question: What type of benchmark is this?
Options:
A) An evaluation based solely on subjective human judgment. B) A standardized test designed to measure an agent's performance against a defined set of criteria and a baseline. C) A casual observation of the agent's behavior during a typical workday. D) An analysis of the agent's code commits over the past month.
Option B is correct. SWE-bench (Software Engineering Benchmark) refers to a standardized testing framework used in agentic evaluation. These benchmarks provide objective metrics for comparing different agents and tracking performance improvements over time. Options A, C, and D are inaccurate representations of benchmarking.
26 / 45
PR Description
Subject: Agent Performance Update - Order Processing
Body:
Agent successfully processed 127 out of 130 orders. However, the agent exhibited a high rate of 're-routing' – specifically, 5 orders were incorrectly directed to the shipping department instead of customer support. Further investigation into the agent's decision-making process is required.
Note: Agent ID: 7492
This question tests understanding of how 're-routing' is used in agentic evaluation. It's not simply about overall success rate; it highlights a specific *deviation* from the intended process – in this case, incorrect routing. The correct answer focuses on the need to examine the agent's decision-making logic because that's where the problem lies, correcting the misconception that 'success' always equates to perfect adherence to a defined workflow.
27 / 45
Reviewer: "The agent's action log shows it repeatedly attempted to use the sendEmail function even after receiving a 'no recipient' error. This suggests a lack of robustness in its handling of API responses." What does 'action log' refer to in this context, and why is this observation significant for evaluating the agent's performance?
Action log refers to a precise record of every function call or API interaction made by the agent. This is crucial because it allows developers to understand *how* the agent attempted to solve a problem, not just the outcome. Observing repeated attempts after an error (like `sendEmail` failing) highlights a potential weakness in the agent's logic – namely, its inability to gracefully handle API errors and retry appropriately, impacting robustness.
28 / 45
**Scenario:** Your team reports 'The agent completed the task in 8 steps vs. the expected 5.'
Question: Why does step count matter in agentic evaluation?
Options:
A) Step count is irrelevant; only the outcome of the task matters. B) Step count indicates potential inefficiencies and deviations from expected behavior, providing a metric for comparison and optimization. C) Agents should always strive to complete tasks in fewer steps, regardless of context or complexity. D) Step count measures the agent's intelligence level, reflecting its ability to solve complex problems.
This question tests understanding of metrics in agentic evaluation. Option B is correct because step count provides a quantifiable measure of efficiency and potential deviations from the intended execution path. Options A, C, and D are incorrect as they focus on irrelevant factors or misinterpretations of the metric's purpose.
29 / 45
**Scenario:** A colleague mentions 'the agent's reasoning trace shows the agent misidentified the goal.'
Question: What is a reasoning trace?
Options:
A) A detailed report of the agent's financial transactions. B) A log of all commands executed by the agent, regardless of their relevance to the task. C) A record of the steps the agent took to reach its decision-making process and identify the goal. D) A summary of user feedback regarding the agent's performance.
The correct answer is C. A reasoning trace specifically documents *how* an agent arrived at a decision or goal. It's crucial for debugging and understanding the agent's thought process, not just its actions. Options A, B, and D describe different types of logs or feedback, but don't represent the core concept of a 'reasoning trace'.
30 / 45
**Scenario:** Your team says 'We benchmark the agent on SWE-bench.'
Question: What type of benchmark is this?
Options:
A) An evaluation based solely on subjective human judgment. B) A standardized test designed to measure an agent's performance against a defined set of criteria and a baseline. C) A casual observation of the agent's behavior during a typical workday. D) An analysis of the agent's code commits over the past month.
Option B is correct. SWE-bench (Software Engineering Benchmark) refers to a standardized testing framework used in agentic evaluation. These benchmarks provide objective metrics for comparing different agents and tracking performance improvements over time. Options A, C, and D are inaccurate representations of benchmarking.
31 / 45
PR Description
Subject: Agent Performance Update - Order Processing
Body:
Agent successfully processed 127 out of 130 orders. However, the agent exhibited a high rate of 're-routing' – specifically, 5 orders were incorrectly directed to the shipping department instead of customer support. Further investigation into the agent's decision-making process is required.
Note: Agent ID: 7492
This question tests understanding of how 're-routing' is used in agentic evaluation. It's not simply about overall success rate; it highlights a specific *deviation* from the intended process – in this case, incorrect routing. The correct answer focuses on the need to examine the agent's decision-making logic because that's where the problem lies, correcting the misconception that 'success' always equates to perfect adherence to a defined workflow.
32 / 45
Reviewer: "The agent's action log shows it repeatedly attempted to use the sendEmail function even after receiving a 'no recipient' error. This suggests a lack of robustness in its handling of API responses." What does 'action log' refer to in this context, and why is this observation significant for evaluating the agent's performance?
Action log refers to a precise record of every function call or API interaction made by the agent. This is crucial because it allows developers to understand *how* the agent attempted to solve a problem, not just the outcome. Observing repeated attempts after an error (like `sendEmail` failing) highlights a potential weakness in the agent's logic – namely, its inability to gracefully handle API errors and retry appropriately, impacting robustness.
33 / 45
**Scenario:** Your team reports 'The agent completed the task in 8 steps vs. the expected 5.'
Question: Why does step count matter in agentic evaluation?
Options:
A) Step count is irrelevant; only the outcome of the task matters. B) Step count indicates potential inefficiencies and deviations from expected behavior, providing a metric for comparison and optimization. C) Agents should always strive to complete tasks in fewer steps, regardless of context or complexity. D) Step count measures the agent's intelligence level, reflecting its ability to solve complex problems.
This question tests understanding of metrics in agentic evaluation. Option B is correct because step count provides a quantifiable measure of efficiency and potential deviations from the intended execution path. Options A, C, and D are incorrect as they focus on irrelevant factors or misinterpretations of the metric's purpose.
34 / 45
**Scenario:** A colleague mentions 'the agent's reasoning trace shows the agent misidentified the goal.'
Question: What is a reasoning trace?
Options:
A) A detailed report of the agent's financial transactions. B) A log of all commands executed by the agent, regardless of their relevance to the task. C) A record of the steps the agent took to reach its decision-making process and identify the goal. D) A summary of user feedback regarding the agent's performance.
The correct answer is C. A reasoning trace specifically documents *how* an agent arrived at a decision or goal. It's crucial for debugging and understanding the agent's thought process, not just its actions. Options A, B, and D describe different types of logs or feedback, but don't represent the core concept of a 'reasoning trace'.
35 / 45
**Scenario:** Your team says 'We benchmark the agent on SWE-bench.'
Question: What type of benchmark is this?
Options:
A) An evaluation based solely on subjective human judgment. B) A standardized test designed to measure an agent's performance against a defined set of criteria and a baseline. C) A casual observation of the agent's behavior during a typical workday. D) An analysis of the agent's code commits over the past month.
Option B is correct. SWE-bench (Software Engineering Benchmark) refers to a standardized testing framework used in agentic evaluation. These benchmarks provide objective metrics for comparing different agents and tracking performance improvements over time. Options A, C, and D are inaccurate representations of benchmarking.
36 / 45
PR Description
Subject: Agent Performance Update - Order Processing
Body:
Agent successfully processed 127 out of 130 orders. However, the agent exhibited a high rate of 're-routing' – specifically, 5 orders were incorrectly directed to the shipping department instead of customer support. Further investigation into the agent's decision-making process is required.
Note: Agent ID: 7492
This question tests understanding of how 're-routing' is used in agentic evaluation. It's not simply about overall success rate; it highlights a specific *deviation* from the intended process – in this case, incorrect routing. The correct answer focuses on the need to examine the agent's decision-making logic because that's where the problem lies, correcting the misconception that 'success' always equates to perfect adherence to a defined workflow.
37 / 45
Reviewer: "The agent's action log shows it repeatedly attempted to use the sendEmail function even after receiving a 'no recipient' error. This suggests a lack of robustness in its handling of API responses." What does 'action log' refer to in this context, and why is this observation significant for evaluating the agent's performance?
Action log refers to a precise record of every function call or API interaction made by the agent. This is crucial because it allows developers to understand *how* the agent attempted to solve a problem, not just the outcome. Observing repeated attempts after an error (like `sendEmail` failing) highlights a potential weakness in the agent's logic – namely, its inability to gracefully handle API errors and retry appropriately, impacting robustness.
38 / 45
**Scenario:** Your team reports 'The agent completed the task in 8 steps vs. the expected 5.'
Question: Why does step count matter in agentic evaluation?
Options:
A) Step count is irrelevant; only the outcome of the task matters. B) Step count indicates potential inefficiencies and deviations from expected behavior, providing a metric for comparison and optimization. C) Agents should always strive to complete tasks in fewer steps, regardless of context or complexity. D) Step count measures the agent's intelligence level, reflecting its ability to solve complex problems.
This question tests understanding of metrics in agentic evaluation. Option B is correct because step count provides a quantifiable measure of efficiency and potential deviations from the intended execution path. Options A, C, and D are incorrect as they focus on irrelevant factors or misinterpretations of the metric's purpose.
39 / 45
**Scenario:** A colleague mentions 'the agent's reasoning trace shows the agent misidentified the goal.'
Question: What is a reasoning trace?
Options:
A) A detailed report of the agent's financial transactions. B) A log of all commands executed by the agent, regardless of their relevance to the task. C) A record of the steps the agent took to reach its decision-making process and identify the goal. D) A summary of user feedback regarding the agent's performance.
The correct answer is C. A reasoning trace specifically documents *how* an agent arrived at a decision or goal. It's crucial for debugging and understanding the agent's thought process, not just its actions. Options A, B, and D describe different types of logs or feedback, but don't represent the core concept of a 'reasoning trace'.
40 / 45
**Scenario:** Your team says 'We benchmark the agent on SWE-bench.'
Question: What type of benchmark is this?
Options:
A) An evaluation based solely on subjective human judgment. B) A standardized test designed to measure an agent's performance against a defined set of criteria and a baseline. C) A casual observation of the agent's behavior during a typical workday. D) An analysis of the agent's code commits over the past month.
Option B is correct. SWE-bench (Software Engineering Benchmark) refers to a standardized testing framework used in agentic evaluation. These benchmarks provide objective metrics for comparing different agents and tracking performance improvements over time. Options A, C, and D are inaccurate representations of benchmarking.
41 / 45
PR Description
Subject: Agent Performance Update - Order Processing
Body:
Agent successfully processed 127 out of 130 orders. However, the agent exhibited a high rate of 're-routing' – specifically, 5 orders were incorrectly directed to the shipping department instead of customer support. Further investigation into the agent's decision-making process is required.
Note: Agent ID: 7492
This question tests understanding of how 're-routing' is used in agentic evaluation. It's not simply about overall success rate; it highlights a specific *deviation* from the intended process – in this case, incorrect routing. The correct answer focuses on the need to examine the agent's decision-making logic because that's where the problem lies, correcting the misconception that 'success' always equates to perfect adherence to a defined workflow.
42 / 45
Reviewer: "The agent's action log shows it repeatedly attempted to use the sendEmail function even after receiving a 'no recipient' error. This suggests a lack of robustness in its handling of API responses." What does 'action log' refer to in this context, and why is this observation significant for evaluating the agent's performance?
Action log refers to a precise record of every function call or API interaction made by the agent. This is crucial because it allows developers to understand *how* the agent attempted to solve a problem, not just the outcome. Observing repeated attempts after an error (like `sendEmail` failing) highlights a potential weakness in the agent's logic – namely, its inability to gracefully handle API errors and retry appropriately, impacting robustness.
43 / 45
**Scenario:** Your team reports 'The agent completed the task in 8 steps vs. the expected 5.'
Question: Why does step count matter in agentic evaluation?
Options:
A) Step count is irrelevant; only the outcome of the task matters. B) Step count indicates potential inefficiencies and deviations from expected behavior, providing a metric for comparison and optimization. C) Agents should always strive to complete tasks in fewer steps, regardless of context or complexity. D) Step count measures the agent's intelligence level, reflecting its ability to solve complex problems.
This question tests understanding of metrics in agentic evaluation. Option B is correct because step count provides a quantifiable measure of efficiency and potential deviations from the intended execution path. Options A, C, and D are incorrect as they focus on irrelevant factors or misinterpretations of the metric's purpose.
44 / 45
**Scenario:** A colleague mentions 'the agent's reasoning trace shows the agent misidentified the goal.'
Question: What is a reasoning trace?
Options:
A) A detailed report of the agent's financial transactions. B) A log of all commands executed by the agent, regardless of their relevance to the task. C) A record of the steps the agent took to reach its decision-making process and identify the goal. D) A summary of user feedback regarding the agent's performance.
The correct answer is C. A reasoning trace specifically documents *how* an agent arrived at a decision or goal. It's crucial for debugging and understanding the agent's thought process, not just its actions. Options A, B, and D describe different types of logs or feedback, but don't represent the core concept of a 'reasoning trace'.
45 / 45
**Scenario:** Your team says 'We benchmark the agent on SWE-bench.'
Question: What type of benchmark is this?
Options:
A) An evaluation based solely on subjective human judgment. B) A standardized test designed to measure an agent's performance against a defined set of criteria and a baseline. C) A casual observation of the agent's behavior during a typical workday. D) An analysis of the agent's code commits over the past month.
Option B is correct. SWE-bench (Software Engineering Benchmark) refers to a standardized testing framework used in agentic evaluation. These benchmarks provide objective metrics for comparing different agents and tracking performance improvements over time. Options A, C, and D are inaccurate representations of benchmarking.
What will I practice in "Agentic Evaluation Vocabulary"?
This is an AI Agents Language exercise set. It walks through 45 scenario-based multiple-choice questions built around real usage of AI Agents Language terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 45 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the AI Agents Language vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more AI Agents Language exercises?
See the AI Agents Language exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — AI Agents Language vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.