Lesson 2 of 8
Tools and Actions
An agent should receive the smallest set of tools and actions required to accomplish its bounded goal.
Active reading
Tool
A capability the agent may call.
Action
A concrete operation.
Permission
What is allowed or forbidden.
Tools define what the agent can actually do
A model can propose actions, but tools turn proposals into effects. That makes tool design a security and reliability boundary.
Prefer narrow tools such as “search approved documents” over broad capabilities such as unrestricted web or shell access when the task does not need them.
Example
Research agent: allowed = search approved sources, save notes. Not allowed = send emails or modify accounts.
Quick check
Explain this lesson back in one sentence before continuing. If you cannot, reread the example and key takeaway.
Common mistake
Do not grant broad permissions merely because they are convenient during development.
Key takeaway
Give an agent the minimum tools and permissions that match its goal.