diff --git a/routines/templates/meeting-prep.md b/routines/templates/meeting-prep.md
index eced6228a..306442b3f 100644
--- a/routines/templates/meeting-prep.md
+++ b/routines/templates/meeting-prep.md
@@ -14,7 +14,7 @@ The routine prompt already includes an `Upcoming Event` section with the title,
 
 1. Read the upcoming event details in the prompt carefully.
 2. If you need broader context, call `sol call calendar list $day_YYYYMMDD` to see the surrounding schedule.
-3. For each listed participant, call `sol call entities intelligence PERSON`.
+3. For each listed participant, call `sol call entities intelligence PERSON --brief`.
 4. Use `sol call journal search QUERY -n 10` to look for recent mentions of the meeting topic, project, or participants.
 5. If a configured facet seems especially relevant, use `sol call journal news FACET --day $day_YYYYMMDD`.
 6. Use `sol call todos list` only if pending action items are directly relevant to the meeting.
diff --git a/routines/templates/morning-briefing.md b/routines/templates/morning-briefing.md
index 3f17ded18..031274733 100644
--- a/routines/templates/morning-briefing.md
+++ b/routines/templates/morning-briefing.md
@@ -17,7 +17,7 @@ This is not a conversation. Gather the information, synthesize it, and write a c
 3. Call `sol call todos list` to see pending action items across facets.
 4. Call `sol call identity pulse` to capture current narrative, priorities, and needs-you items.
 5. Call `sol call journal search "" -a followups -n 10` to find recent follow-up items.
-6. For each person on today's calendar, call `sol call entities intelligence PERSON`.
+6. For each person on today's calendar, call `sol call entities intelligence PERSON --brief`.
 7. If a facet needs more detail, call `sol call journal news FACET --day $day_YYYYMMDD`.
 
 ## Synthesize
diff --git a/talent/triage.md b/talent/triage.md
index 7a7839e15..0503bfe33 100644
--- a/talent/triage.md
+++ b/talent/triage.md
@@ -34,7 +34,7 @@ You are given context about the owner's current app, URL path, and facet. Use th
 - `sol call entities observe ENTITY CONTENT --facet FACET` — Record an observation.
 - `sol call entities strength [--facet FACET] [--since YYYYMMDD] [--limit N]` — Rank entities by relationship strength.
 - `sol call entities search [--query TEXT] [--type TYPE] [--facet FACET] [--since YYYYMMDD] [--limit N]` — Search entities by text, type, or facet.
-- `sol call entities intelligence ENTITY [--facet FACET]` — Full intelligence briefing for an entity (returns JSON — synthesize into natural language).
+- `sol call entities intelligence ENTITY [--facet FACET] [--brief]` — Intelligence briefing for an entity (returns JSON — synthesize into natural language). Use --brief for concise lookups.
 
 ### Journal
 - `sol call journal events [DAY] [-f FACET]` — List events with participants, times, and summaries.
@@ -55,7 +55,7 @@ You are given context about the owner's current app, URL path, and facet. Use th
 - For entity intelligence briefings, synthesize the JSON output into a concise natural-language summary — do not dump raw JSON.
 - **Pre-meeting briefings**: When the owner asks "brief me on my next meeting", "who am I meeting?", or similar:
   1. Run `sol call journal events` to find upcoming events with participants.
-  2. For each participant, run `sol call entities intelligence PARTICIPANT` to gather background.
+  2. For each participant, run `sol call entities intelligence PARTICIPANT --brief` to gather background.
   3. Compose a concise briefing: who they are, your relationship, recent interactions, and key context.
   Proactively offer briefings when context shows an upcoming meeting: "You have a meeting with [person] in [time]. Want me to brief you?"
 - **Support**: When the owner reports a problem ("this isn't working", "I found a bug", "something's broken"), wants to file a ticket, or wants to give feedback, handle it in-place — search KB, run diagnostics, draft and submit a ticket with the owner's approval.