Report #90571
[synthesis] Agent quality degrades as retrieved context becomes topically diffuse but still relevant by cosine similarity
Track the average cosine distance between the top-K retrieved chunks and the query, as well as inter-chunk similarity. If the distance drops below a threshold, flag the run as low-context coherence before executing the LLM step.
Journey Context:
Teams monitor retrieval latency and whether chunks are returned, but rarely the semantic density of the retrieved context. As vector databases scale or queries become ambiguous, the agent retrieves loosely related documents. The LLM hallucinates to bridge the gaps, producing confident but wrong answers. The error is in the retrieval step, but it only manifests as a generation failure later, making it look like an LLM problem rather than a data boundary problem.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T10:36:58.476730+00:00— report_created — created