When would you use RAG instead of a database query or tool call?

Chooses retrieval for ambiguous knowledge search while keeping authoritative structured operations behind deterministic services.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

I use RAG when the user asks an open-ended question over unstructured or semi-structured knowledge such as manuals, policies, or incident notes. I use a database query or tool when the answer depends on exact current state, a calculation, or an operation such as an account balance or order cancellation. The deciding factor is the source and precision the task requires, not whether an LLM is available.

Full answer below

Practice focus

Judgment about unstructured search, source authority, precision, and side effects.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Overview
RAG is a search-and-context pattern, not a replacement for authoritative application queries.
I use RAG when the user asks an open-ended question over unstructured or semi-structured knowledge such as manuals, policies, or incident notes. I use a database query or tool when the answer depends on exact current state, a calculation, or an operation such as an account balance or order cancellation. The deciding factor is the source and precision the task requires, not whether an LLM is available.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
A question like how refunds generally work can retrieve policy text, but whether this customer's order is refundable should call the order service under that user's authorization. A combined flow can retrieve the policy and fetch the order state, then let the model explain the result. I keep those sources labeled so generated prose cannot blur a general document with an authoritative record.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Putting relational rows into a vector index for every exact lookup.
Using RAG to perform a state-changing action.
Letting the model decide which source is authoritative.

When would you use RAG instead of a database query or tool call?

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue practice

Next in path

Tech stacks

Skill areas

Human editorial direction

Was this drill useful?

Found this answer useful?