AI

AI Agents

A practical guide to understanding what AI agents are and how they differ from standard AI features.

What AI agents are, how they work, and what product and design teams need to understand when building or evaluating agentic AI features.

22 May 20265 min read

What it is

An AI agent is a that uses a language to plan and execute a sequence of actions to complete a goal, rather than simply responding to a single .

Where a standard AI involves a user asking a question and the providing an answer, an agent can take that goal and break it down into steps, use tools to gather information or take actions, and iterate until the task is complete.

An agent might the web, read a document, write and run code, fill in a form, send a message, or call an external — all as part of completing a single instruction.

The key distinction is autonomy. An agent acts, rather than just responding.

This makes agents powerful for complex, multi-step tasks. It also introduces new design challenges around , oversight, and failure handling that do not exist in simpler AI .

When to use it

Understand when agentic AI is appropriate.

It is most relevant when:

A task involves multiple steps that would otherwise require human coordination
The task is repeated frequently enough to justify automation
The AI needs to interact with external tools, data, or systems
Human effort on the task is high relative to the value of each instance

It is less relevant when:

A task can be completed with a single prompt and response
The task involves high-stakes, irreversible actions that need human sign-off
The workflow is unpredictable enough that structured automation is unreliable

Key takeaway

Agents are powerful when tasks are structured, repetitive, and recoverable. They are risky when tasks are ambiguous, high-stakes, or difficult to reverse.

How it works

Understand the basic mechanism. An AI agent uses a language as its reasoning engine. Given a goal, the model decides what steps to take, calls the appropriate tools, observes the results, and decides what to do next.

This loop — observe, plan, act, observe — continues until the goal is achieved or the agent reaches a point where it cannot proceed.

Agents require access to tools, which might be web , code execution, file reading, API calls, or any other defined by the . The agent decides which tools to use and when.

What this means for designers and product teams. Designing an AI agent means designing the , the tools available, the on what the agent can do, and the points at which a human should be involved.

Agents can fail in novel ways. They can take wrong turns mid-task, use tools incorrectly, or produce errors that compound across steps. Unlike a single wrong answer, a wrong action taken early in an agentic can create problems that are difficult to unwind.

What to look for

Focus on:

Task boundaries — whether the agent's scope is clearly defined
Tool access — whether the agent has access only to what it needs
Failure handling — what happens when a step fails or produces unexpected results
Human checkpoints — where human review or approval is required
Reversibility — whether actions taken by the agent can be undone if needed

Where it goes wrong

Most issues come from: Giving an agent broad access and minimal oversight is not a design decision — it is a risk.

Poorly defined task boundaries leading to unpredictable behaviour
Excessive tool access beyond what the task requires
No checkpoints for human review at high-risk steps
Insufficient testing across edge cases and failure modes
Assuming agents will handle ambiguous situations gracefully

What you get from it

Understanding AI agents gives you:

A clearer framework for deciding when agentic AI is appropriate
Better ability to brief and evaluate agentic features
A foundation for designing safe, well-bounded autonomous workflows
More informed conversations with engineers about agent architecture and risk

Key takeaway

AI agents are not just smarter chatbots. They introduce a fundamentally different design challenge that requires thinking carefully about what the agent can do, what it cannot, and what happens when things go wrong.

FAQ

Common questions

A few practical answers to the questions that usually come up around this method.

What is an AI agent?

An AI agent is a that uses a language to plan and execute a sequence of actions to complete a goal. Rather than answering a single question, an agent can take that goal, break it into steps, use tools, and act on the results — iterating until the task is done.

How is an AI agent different from a chatbot?

A chatbot responds to with text. An agent acts. It can take real actions — searching the web, running code, calling APIs, writing files — as part of completing a task. The difference is between answering a question and completing a job.

What kind of tools can an AI agent use?

It depends on what tools have been connected to it. Common examples include web , code execution, file reading and writing, API calls to external , calendar and email access, and database queries. The agent's are defined by the tools it has been given access to.

Are AI agents safe?

They can be, when designed well. The key risks are that agents can take actions that are difficult to reverse, that errors can compound across steps, and that poorly constrained agents may take actions outside their intended scope. Good agent design involves clear task boundaries, appropriate human oversight, and extensive testing.

Do I need technical knowledge to work on AI agent products?

Not deeply technical knowledge, but you need to understand the principles. Knowing what tools the agent has access to, where human oversight is needed, how failure modes are handled, and what the intended scope of the agent is are all design and product decisions — not just engineering ones.

Quick take

AI agents go beyond answering questions — they take actions, use tools, and complete tasks on your behalf, which changes what is possible and what can go wrong.

Related Services

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services. The work usually starts where things have become harder than they need to be: unclear journeys, inconsistent products, competing priorities, or teams trying to move forward without a clear direction. I help simplify the problem, shape the right next step, and turn complexity into something people can actually use.

Previous feedback

Will Parkhouse

Senior Content Designer

01/20