💬 In plain words: The Agentforce AI model chooses which action to call by reading its description. It does not look at the action's name, and it does not read the underlying code. Therefore, an action description is not documentation for human developers—it is the strict selection criteria the model uses to choose between a dozen different tools. 📌 Example: Naming an action "Creates an appointment" is incredibly weak. A strong description looks like this: "Books a field crew visit for a specific meter on a chosen date. Returns the booking reference and confirmed date. Use only after checking whether the fault is on the customer's side." 🎬 Real-Life Example: The Action That Never Got Called The Old/Bad Way: A development team built a flawless Apex action to check for system outages. They lazily set the description to: "Outage utility method." Why it failed: The AI model relies purely on description...
Agentforce