An agent wraps an LLM in a loop that reasons, calls tools, observes results, and repeats until done. The loop, not the model, is what makes it agentic.
Imagine asking a friend a hard question. A plain LLM call is like getting one shot to answer from memory: you reply once and that is it. An agent is like that same friend with a phone, a search engine, and a calculator. They can think, look something up, check the answer, look up something else, and keep going until they are confident. They are not smarter than before, they just have permission to take more than one step and use tools along the way. The repeating cycle of think, act, observe, decide is what makes a system an agent. Without that cycle, you just have a single answer from a single shot, no matter how powerful the model is.
Detailed answer & concept explanation~4 min readEverything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example.
Everything important, quickly.
Start by stating that agency is a runtime architectural property, not a model property. Name the four-move loop, contrast with one-shot calls and fixed chains, walk through why each distractor is wrong, and finish by noting how function calling has made the agent loop easier to implement without changing what makes it an agent.
Real products, models, and research that use this idea.
- Claude's tool use API lets a single model power both one-shot Q&A and full agent loops, the difference is whether the caller iterates on tool_use results.
- OpenAI's Assistants API exposes a thread with an explicit run loop, making the agent architecture visible in the SDK shape itself.
- LangGraph's prebuilt ReAct agent is essentially a state machine that wraps any function-calling LLM, with no model-side changes required.
- Cursor's coding agent and Devin both use the same frontier models that power chat products, the difference is the agent runtime around them.
What an interviewer would ask next. Try answering before peeking at the approach.
QIf a chain calls a single tool and returns, is that an agent? Why or why not?
QHow does function calling support in modern LLMs change the agent architecture compared to early ReAct prompting?
Don't say thisRed flags and common mistakes that signal junior thinking. Click to expand.
Red flags and common mistakes that signal junior thinking. Click to expand.
Confusing model capability with system architecture. Bigger or fine-tuned models do not become agents, the loop with tools and observations is what turns any LLM into an agent.
The night-before-the-interview bullets. Scan these on the way to the call.
Primary sources. Skim if you want the original framing.
Same topic, related formats. Practice these next.