Action execution lets an AI agent interact with external systems to carry out tasks, rather than merely describe what a person could do. It bridges the gap between an LLM’s understanding of a request and completing it through a tool such as an API or calendar. section 6.1.2 section 6.1.4
Retrieval and action serve different purposes: retrieval brings information into a response, while action changes state in an external system. An agent might retrieve flight options, then book a selected flight; retrieval-augmented generation alone cannot complete the booking. section 6.2.3 section 6.1.4
Scheduling a meeting
A standalone LLM can suggest emailing a team but cannot send an invitation. An agent can connect to a calendar, check availability, schedule the meeting, and send invites. section 6.1.2 section 6.1.4
External tools can also ground answers in current information: an agent can query a weather API instead of guessing at today’s conditions. For multi-step tasks, workflow orchestration coordinates the actions; production systems also need controls and monitoring to guard against loops that repeat tool calls without progress. section 6.2.3 section 6.0 section 6.1.4
