pub const SEARCH: &str = "Search graph nodes by text — names, keys, paths, and captured content (doc comments, \
README/ADR/blueprint prose). Returns the top matches with keys and, for content-bearing \
nodes, a short `snippet` of the node's actual content to ground your answer; curated \
ADRs/blueprints and READMEs rank first, so this is the entry point for \"what is X / why\" \
questions. `limit` is 1-25 (default 10) — no unlimited setting.";Expand description
search.
“Read the snippet, and call explain on a returned key for the full
content” went in #675: the system turn the served surface wraps this listing
in already says it, in more words and to every tool at once — “read each hit’s
snippet or call explain on its key to read the node’s actual content BEFORE
describing it” (rto_serve::advertised_system_prompt). Two statements of one
instruction is what the prompt was paying for twice.