Tool workflow
Connect a model to a narrow, observable tool when a bounded action is necessary.
What this pattern means
Connect a model to a narrow, observable tool when a bounded action is necessary. Choose it because it is the least complex approach that satisfies the task—not because it uses the most capable model.
When it fits
- The permitted action and data scope are explicit.
- The workflow can preview, validate, and roll back changes.
- A deterministic tool contract constrains model-proposed arguments.
When it does not fit
- Permissions are broad or unclear.
- The action is irreversible or cannot be monitored.
Required controls
- Use least-privilege permissions.
- Validate tool arguments and preview writes before execution.
Autonomy limit
The maximum v1 autonomy is Bounded reversible action. A task-specific rule may impose a stricter cap.
Minimum evaluation
Test permission boundaries, malformed arguments, duplicate execution, rollback, and escalation paths.
Example
Update selected CRM fields after a person approves a preview.
Reassess tool workflow whenever the purpose, evidence, data class, decision owner, or external-action boundary changes.
