Key Principles
Be Specific
Vague instructions lead to unpredictable results.
Show Examples
Demonstrate the expected behavior with concrete examples.
Define Boundaries
Clearly state what the agent should and shouldn’t do.
Explain Context
Help the agent understand why certain rules exist.
Instruction Structure
A good set of instructions typically includes:1
Mission Statement
One clear sentence about what the agent does.
2
Key Responsibilities
The main tasks the agent handles.
3
Guidelines
How to handle common situations.
4
Boundaries
What the agent should never do.
5
Escalation
When and how to ask for human help.
Examples
- Good Instructions
- Bad Instructions
Level of Detail
The detail level controls predictability vs. flexibility:| More Detail | Less Detail |
|---|---|
| More predictable behavior | More flexible problem-solving |
| Less room for creativity | Can handle unexpected situations |
| Easier to audit | May surprise you (good or bad) |
Common Mistakes
Too vague
Too vague
“Handle customer emails” → What does “handle” mean? Which customers?
Conflicting rules
Conflicting rules
“Always respond quickly” + “Take time to research thoroughly”
Missing edge cases
Missing edge cases
What if the data is incomplete? What if the system is down?
No escalation path
No escalation path
Agent doesn’t know when to ask for help.
Let the Agent Help
Remember: agents can write their own instructions based on conversation. Often, the best approach is:- Describe what you want
- Let the agent draft instructions
- Review and refine together
- Test and iterate

