Why is the Leave and Absence Policy Advisor Configured as a Worker Agent Instead of a RAG Agent?

Summary:

Hi Experts,

I noticed that the Leave and Absence Advisor Agent is configured by default as a Worker Agent rather than a RAG (Retrieval-Augmented Generation) Agent.

Could someone help clarify the reasoning behind this design choice? Specifically:

• What are the functional or architectural considerations for classifying it as a Worker Agent?
• Are there limitations or scenarios where a RAG-based approach would not be suitable for Leave and Absence policy use cases?
• Is there any recommended approach to extend or adapt this agent using RAG if required?

Any insights or documentation references would be greatly appreciated.

Thanks in advance!

Regards,