An AI agent is an LLM given a goal, a set of tools, and permission to take several steps on its own. A single LLM call is one turn: text in, text out, then it is over.
Single LLM call
Agent
Steps
Exactly one
Keeps going until the goal is met
Who picks the next action
Your code
The model, at runtime
Tools
None, or one round you handle
Called repeatedly, results fed back in
State
Stateless
Carries context across steps
Cost and latency
Predictable
Varies run to run
The real difference is control. You trade a predictable path for the ability to handle tasks whose steps are unknown up front. That is why every agent needs step limits, spend budgets, and logs.
Rewriting in plainer words…
This answer doesn't lend itself to a diagram - it reads best . No credits were charged.
An AI agent is an LLM with a goal, a set of tools, and permission to take several steps on its own.
A single LLM call is one turn. Text goes in, text comes out, and it's over.
In an agent, the model picks the next action at runtime, calls tools, reads the results and keeps going until the goal is met.
It carries context from step to step, while a single call is stateless and your code decides what happens next.
So the real difference is control. My code no longer picks the path, the model does.
That lets you handle tasks whose steps you can't know up front, but cost and latency vary run to run, so every agent needs step limits, spend budgets and logs.
Weak answers to avoid
Treats one function call as an agentYour code handling one round of tool calls is still a single call. It becomes an agent when the model picks the next action repeatedly until the goal is met.
Defines an agent as a chatbot with memoryMemory alone doesn't make an agent. The defining change is who controls the next step. Say the model chooses actions and calls tools in a loop.
Pitches agents as strictly betterAgents give up predictable cost and latency. Say when a single call is enough, and name step limits, spend budgets and logs as the price of using one.
Says 'autonomous AI' with no mechanismBuzzwords don't show understanding. Describe the loop instead. The model picks a tool, your code runs it, the result goes back in, and it repeats.
Interview lens
Likely follow-ups, what you can say, and the weak answers to avoid.