Agents: Role, Goal, Backstory

Multi-agent demos die when every agent is 'a helpful assistant'. Roles are the API of the team.

A newsroom: reporter, editor, fact-checker. Nobody is 'generic writer'.

Visual Workflows

Start here — scroll inside each diagram frame to explore, then use + / − to zoom up to 200% if needed.

100%

Loading diagram...

Scroll inside the frame to explore · use + / − to zoom up to 200%

Key Takeaways

1.A CrewAI Agent is a role contract: who you are, what you must accomplish, and what expertise you bring. Role, goal, and backstory are not flavor text — they change tool choice and refusal behavior.
2.Give tools only to the role that should use them. Overlapping jobs make crews fight. allow_delegation stays false unless this agent is a manager.
3.Agent(role, goal, backstory, tools, llm, allow_delegation, memory, knowledge). Role and goal are injected into the system prompt every turn.
4.Backstory supplies constraints. Tools attach to this agent only.
5.Cap max_iter so a confused role cannot loop forever.

Learn elsewhere

→Tasks
→Agent Delegation
→Tool Calling — Phase 7

Real Example

Scenario

Researcher has search. Writer has no search. Writer cannot silently google and invent sources.

What you would do

In CrewAI, apply Agents: Role, Goal, Backstory to this scenario: Researcher has search. Identify the inputs, run the technique, validate the output, and note one thing you would monitor in production.

Commands

Commands to Remember

role + goal + backstory
Tools belong to one role
No overlapping jobs
Delegation is for managers

Cheat Sheet

Quick recap

quick ref

•Roles are contracts
•Split tools
•Manager delegates
•Writer does not search

Common Mistakes

✕Skipping evaluation for Agents: Role, Goal, Backstory before production
✕No logging or tracing around crewai agents roles steps
✕Ignoring cost and latency implications