Skills
Treat agent descriptions as the routing layer — Agentforce now routes on description quality, not decision trees
Salesforce shipped Multi-Agent Orchestration in Agentforce to GA on June 15, 2026, and its Atlas Reasoning Engine 3.0 routes each request by reading specialist agents' plain-language descriptions rather than fixed decision trees. For any description-routed multi-agent system, the description is the control surface: write specific, capability-scoped descriptions and keep the underlying data clean, because vague descriptions or stale data silently misroute work at scale. Treat description quality and data hygiene as production-critical, not documentation.
Source
↳ Follow the thread