KNOWLEDGE DOSSIER · Méthodologie

Evaluating agents and their limits

WebAI evaluation means testing systems against defined tasks and evidence rather than equating fluency with reliability. Models, retrievers, agents and interfaces need different metrics and appropriate human review.

Edition: 13 November 2026 Extended dossier Scientific review pending
AT A GLANCE
TypeEvaluation of models, agents and RAG systems
AudienceResearchers, educators and engineering teams
01

Define the evaluation target

An application can fail during document retrieval, answer generation, tool selection, approval or final display. Identify components and objectives before choosing metrics. A global success rate does not reveal which step actually failed.

02

Test sets and reproducibility

Prepare representative, negative, ambiguous and contradictory cases with reference answers or evidence. Keep model version, date, parameters, data and annotation methods. A small demo set does not establish robust general performance.

03

Evidence faithfulness

In RAG, measure document retrieval, passage relevance, answer faithfulness and citation validity separately. One supported statement may sit beside unsupported statements; evaluate claims individually.

04

Evaluate acting agents

An agent may write correct prose but perform the wrong operation. Review permissions, execution traces, tool calls, approvals and actual final state. Test environments should isolate sensitive actions and permit cancellation.

05

Metrics and human judgment

Relevance, accessibility, bias, privacy, security and educational quality cannot be captured by a single automated score. Combine technical checks, human review, independent assessment and error analysis. Record disagreement rather than hiding it.

06

Exercise: audit an assistant

Build twenty questions with verified sources, five unanswerable cases and safe adversarial inputs. Compare two setups, classify failures and explain sample limitations. Do not publish only a success rate; show difficult examples too.

HOW IT FITS TOGETHER

Core steps

  1. 01Decompose the system and its risks
  2. 02Build a documented test set
  3. 03Measure components separately
  4. 04Test negative and adversarial cases
  5. 05Request independent human review
  6. 06Publish failures, limitations and versions
CRITICAL THINKING

Three questions to ask

  • Does fluent writing establish accuracy?

  • Was the final action state checked?

  • Are difficult failures reported?

  • Is the evaluation corpus representative?

PRIMARY SOURCES

Read the source documents

Versions, reuse terms and document status can change. Check them on the original sites.