Always retrieving, even when unnecessary: Basic RAG retrieves for every query, including "hello" and "thanks." This adds latency, wastes compute, and can inject irrelevant context that confuses the model. Agentic RAG's first decision point -- whether to retrieve at all -- eliminates this waste.
Trusting all retrieved documents equally: Just because a document was returned by vector search does not mean it is relevant. Cosine similarity can be high for topically related but factually irrelevant documents. Self-RAG's relevance evaluation step is critical for filtering noise.
Single-attempt retrieval: If the first retrieval attempt fails, basic RAG generates from bad context. CRAG's retry mechanisms -- query rewriting, source switching, decomposition -- dramatically improve answer quality for hard queries. Think of it as the model saying "let me search differently" rather than "let me guess."
Ignoring the cost of agentic decisions: Each decision point (route, evaluate, verify) adds latency and token cost. For high-throughput, low-latency applications, a simpler RAG pipeline with good retrieval quality may outperform a complex agentic pipeline that spends more time deciding than answering.