What is Agent Role?
Also called role definition.
An agent role is the scoped function assigned to an agent within a system, defining what it is responsible for, which tools and data it may access, and what it must hand off to others. Roles are structural boundaries rather than descriptive labels, and they are most useful when access permissions actually follow them.
A role and a persona are often conflated but differ in what they control. A persona shapes tone and voice, which is presentation. A role determines scope: which tasks an agent accepts, which tools it may call, which data it may read, and where its responsibility ends. Changing a persona changes how output reads, while changing a role changes what can happen.
Roles carry real value only when enforced outside the prompt. A role stating that an agent handles read only analysis is a suggestion if the agent still holds write credentials, because a confusing input or an unusual instruction can pull it past the stated line. Binding the role to an actual permission set makes the boundary hold regardless of what the model decides.
Well drawn roles are narrow enough to have a clear failure mode. When something goes wrong, it should be obvious which role owned the step, which requires that responsibilities do not overlap. Two roles that both plausibly own the same task produce inconsistent routing and make trajectories hard to read after the fact.
Roles also shape handoffs. If a role's scope ends at a specific point, the receiving role and the information required at the boundary can be specified in advance, which turns an implicit expectation into a checkable contract. Systems without explicit role boundaries tend to accumulate agents that quietly duplicate one another's work.
Key points
- Defines scope and access, not tone or voice
- Only meaningful when backed by real permissions
- Non overlapping roles make failures attributable
- Role boundaries define where handoffs occur
- Overlapping roles cause duplicate and inconsistent work
In practice
In a reporting pipeline, one role queries the warehouse with read only credentials, a second turns query results into narrative, and a third publishes the finished document and holds the only write credential. When a wrong figure appears in a published report, the trajectory shows which of the three produced it, and the writer role could not have altered the underlying data even if instructed to.