diff --git a/agents/AGENTS.md b/agents/AGENTS.md
index c3447af..56099b7 100644
--- a/agents/AGENTS.md
+++ b/agents/AGENTS.md
@@ -133,12 +133,13 @@ on your own. Command forms, flags, dataset sharing and failure modes are in the
   checkout stays first choice when it exists. Never call
   `ask_codebase` on your own — it spawns a nested server-side agent
   (minutes per call, shared vLLM); use it only when explicitly asked.
-- **`ccc` for semantic code search.** Repos containing a `.cocoindex_code/`
-  directory are indexed by `ccc`. Reach for it on conceptual questions ("where
-  is X used / what handles Z"), where a keyword grep would miss indirect usage:
-  `ccc search '<concept>'` from the project root. It is embeddings only: exact
-  strings (UUIDs, ticket IDs, error messages) stay with `grep`/`rg`. Details and
-  gotchas in the `ccc` skill.
+- **`ccc` before `grep` for concept questions.** In a repo with a
+  `.cocoindex_code/` directory, a question about a concept ("where is X
+  handled", "what talks to Y", "which code does Z") starts with
+  `ccc search '<concept>'` from the project root, then `grep` verifies what it
+  found. An exact string (UUID, ticket ID, error message, identifier) goes
+  straight to `grep`/`rg`: ccc is embeddings only and will not find it. Gotchas
+  in the `ccc` skill.
 - **`ccc index` / `ccc init` are read-safe maintenance.** They only write to the
   gitignored `.cocoindex_code/` directory, never to source. Run them without
   confirmation prompts; treat like `grep` for permission purposes.