{"found":true,"collection":"patterns","library_url":"https://www.grokbotdb.com/library/pat.tight-descriptions","generated":"2026-09-06T05:32:11Z","citation":["Quote the record id and its source_url (or provenance if there is no URL).","Include last_verified or observed_at when present. Do not present an old date as current.","If tier is community and confidence is low, say so. Do not launder it into a fact.","If the database does not hold the answer, say that. Do not invent Grok Bot product claims.","Contradictions are data: when conflicts_with is present, report both records rather than picking a favourite.","Deprecated and removed records stay visible. They are history, not current guidance."],"record":{"id":"pat.tight-descriptions","name":"Keep descriptions tight because the chief re-reads them","category":"cost","problem":"A verbose roster is re-read on every routing decision an orchestrator makes.","technique":"Keep every Bot description short and factual. Prune it when you add Bots.","why_it_works":"A chief-of-staff Bot reads the descriptions of every other Bot to decide where to route work, and you pay for each read.","when_to_use":"Any roster with an orchestrator.","manual_ref":"1.1","evidence":"documented","related":["pat.chief-of-staff","pat.short-orchestrator-thread"],"confidence":"high","first_seen":"2026-09-03","last_verified":"2026-09-03"}}