How does CrewAI attach tools to specific agents versus the crew as a whole?

Attempt it

Agent-level (tools=[...] on the Agent) is the default scope. That agent has those tools on every Task it handles. Task-level (tools=[...] on the Task) is a per-Task override. It replaces the agent's tool list for that Task only, useful when one Task needs a narrower or specialized toolkit. There is no tools=[...] on the Crew object itself; the crew is just an aggregate. Resolution: if a Task defines its own tools, those are what the agent gets for that Task; otherwise the agent's tools apply. Practical rule: put broadly useful tools on the Agent (so the agent's role / backstory and toolset are coherent), and use Task-level overrides for specialized cases like 'this Task should ONLY use the search tool, no file system access.'

Your answer

TL;DR

CrewAI tools live on the Agent (default) or the Task (per-Task override that replaces the agent's list); there is no Crew-level tools field.

Memory aid

Sign in to see the mnemonic that makes this stick.

Easy to grasp

Imagine an electrician who carries a big toolbox to every house (the agent's tools). Most days she uses whatever she needs from the box. But for one specific job, rewiring a small fuse, the client says 'please bring only the multimeter and the screwdriver, nothing else'. That note for one job is a task-level override. The crew, in this picture, is just the team's name. The team itself does not own any tools. The people do, and individual jobs can narrow what they bring. Same pattern in CrewAI: agents own tools, tasks can narrow them, and the crew is an aggregator with no toolbox of its own.

Key concepts

Agents LLM Frameworks

Concept explanation~2 min read

Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.

Tool scoping is one of those things every multi-agent framework has to answer, and the answer leaks into how safe and how flexible the framework feels in practice. CrewAI's choice, two scopes (Agent, Task) with no global, is opinionated, and the opinion matters in production.

This dive walks through the resolution rule, why CrewAI chose replacement over merge, the least-privilege pattern that makes Task overrides useful, and the operational footguns that show up when teams grow past two or three Agents. The goal is to leave you with a clear mental model for when to put a tool on an Agent, when to override on a Task, and what to do when you wish there were a Crew-level field.

The two real scopes. Agent default, Task override

CrewAI Agents are constructed with a tools=[...] list. That list is the Agent's standing capability. The set of tools the Agent's role and backstory are written to use. When the Crew runs and the Agent picks up a Task, the Agent's tool list becomes the LLM's tool surface for that turn.

Tasks can also be constructed with a tools=[...] list. When the Agent runs a Task with its own tool list, the Task's list replaces the Agent's list for the duration of that Task. The Agent's tools do not merge in. They are hidden. After the Task ends, the Agent's standing list is restored for the next Task.

This replacement semantics is the part teams miss. It is intentional: the override is meant for narrowing, not for stacking. If you want a Task to have everything the Agent has plus one more tool, you have to write out the full list on the Task, including the Agent's tools.

python

from crewai import Agent, Task, Crew

researcher = Agent(
    role='Senior Researcher',
    goal='...',
    tools=[search_tool, file_tool, calc_tool],   # standing capability
)

sensitive_summary = Task(
    description='Summarise the search results without writing files.',
    agent=researcher,
    tools=[search_tool],   # narrows: file_tool and calc_tool are hidden here
)

Why there is no Crew-level tools field

Resolution rule and the LLM's view

Patterns and footguns at scale

Sign in to unlock the full deep dive.

Situations where this technique stops working.

Sign in to see when this approach fails.

2–4 min · Everything important, quickly.

Sign in to see the quick scan of the deep dive.

Real products, models, and research that use this idea.

CrewAI's own marketing-crew example puts the SerperDevTool on the researcher Agent and overrides per-Task when a step should only summarise, not search again.
Llama-Index Workflows take a different model, tools attach to steps, not agents, closer to a per-Task default with no Agent scope.

Sign in to see more production examples.

What an interviewer would ask next. Try answering before peeking at the approach.

QHow would you enforce 'this Task may not use the file-write tool' if it lived on the Agent?

A

The clean answer is a Task-level override that omits the tool. Replacement semantics handle it. Prompt-level restrictions are not enforceable; the tool surface decides what the LLM can call.

1 more follow-up an interviewer would ask next. Sign in to reveal them.

Red flags & common mistakes

The phrases that signal junior thinking. Click to expand.

Most common mistake

Trying to pass tools=[...] to the Crew constructor expecting them to fan out to every Agent. There is no such kwarg, and the call silently does nothing or raises depending on the version.

Sign in to see all red flags and common mistakes.

60 second bullets to scan on the way to the call.

Agent-level vs Task-level tool scope
Why there is no Crew-level tools field

Sign in to unlock the revision sheet.