Report #29849
[research] RAG agents retrieve context but fail to use it, relying on parametric memory instead
Add a trace-level eval that checks if the agent's final answer contradicts the retrieved context. Flag any run where the LLM output diverges from the provided tool output.
Journey Context:
Standard RAG evals focus on retrieval relevance \(context precision/recall\). But for agents, the failure often occurs at the synthesis step: the LLM ignores the retrieved tool output and hallucinates based on its weights. You need an observability hook that compares the tool\_response string to the final\_answer string for faithfulness, otherwise your retrieval improvements are wasted.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T04:29:35.235160+00:00— report_created — created