Agent evaluation logopeterindia.net
Knowledge Hub

Evaluating & Improving Agentic Applications

How to measure and improve AI agents: evaluation frameworks and platforms, benchmarks, graders and LLM-as-judge methods, and techniques that turn failures into better prompts, tools and models. Grouped by purpose, not ranked.

82 topics•7 categories•Updated November 2026

1. Foundations: What to Evaluate in an Agent

11 entries

Guidance on measuring agents: outcomes, trajectories, tool use and cost. Evaluate the final result and the path the agent took to reach it.

2. Open-Source Evaluation Frameworks

19 entries

Libraries you run yourself to score agents and LLM applications. Pick one that fits your language, tracing and CI setup.

3. Evaluation and Observability Platforms

14 entries

Hosted or self-hostable platforms that combine tracing, datasets, evals and monitoring. Most support OpenTelemetry-style traces and CI gating.

4. Agent Benchmarks

12 entries

Public benchmarks for measuring agent capability across tool use, web, code and computer tasks. Use them to compare models and agents, then build your own for your tasks.

5. Evaluation Methods: Graders, Trajectories and LLM-as-Judge

8 entries

How agent outputs and trajectories are scored. Combine code-based checks, model graders and human review.

6. Improving Agents: Feedback, Optimisation and Self-Improvement

10 entries

Techniques and tools that use evaluation results to make agents better. Close the loop: evaluate, find the failure, change the prompt, tools or model, then re-test.

7. Related Pages on This Site

8 entries

Neighbouring directories for operating and securing agents. Evaluation sits beside observability, guardrails and operations.

Frequently Asked Questions

How do you evaluate an agentic application?

Define tasks with clear success criteria, run the agent in a controlled environment, and score both the final outcome and the trajectory: the tools called, their arguments, the order of steps, cost and latency. Combine code-based checks, model graders and human review, and run the suite on every change.

How is evaluating an agent different from evaluating an LLM?

A model answers once, while an agent takes many steps, calls tools and changes state. You must grade the end state and the path, handle non-determinism by running tasks several times, and check side effects such as files or records changed.

What are the main evaluation frameworks for agents?

Open-source options include DeepEval, Ragas, promptfoo, UK AISI Inspect, OpenAI Evals, OpenEvals and AgentEvals, Arize Phoenix, Opik and TruLens. Platforms that add tracing, datasets and monitoring include LangSmith, Langfuse, Braintrust, Galileo and Weights & Biases Weave.

Which metrics matter for agents?

Common ones are task completion, tool-call accuracy, argument correctness, step efficiency, goal accuracy, faithfulness to retrieved context, safety violations, cost and latency. Pick a few that match how users judge success rather than tracking everything.

Can an LLM judge an agent's work?

Yes, LLM-as-judge and agent-as-judge methods are widely used, but judges show biases such as favouring longer answers. Calibrate them against human labels, use clear rubrics, and prefer deterministic checks where a result can be verified by code.

Which benchmarks test agents?

Public benchmarks include SWE-bench for code, tau-bench for tool-agent-user dialogue, GAIA for assistant tasks, WebArena for web tasks, OSWorld for computer use, Terminal-Bench for command line work and the Berkeley Function Calling Leaderboard. They compare models, but your own tasks should decide what ships.

How do you improve an agent after evaluating it?

Read failed traces, group the errors, then change the prompt, tool descriptions, context, model or workflow and re-run the suite. Techniques such as DSPy, GEPA, Reflexion and reinforcement fine-tuning automate parts of this loop against a metric.

How current is this list?

Links were checked in November 2026. A few sites block automated checks and may need a manual click. This page is a resource list, not engineering advice, and tool descriptions reflect each project's own positioning.