# Tool Boundary Checklist

## Before the tool runs
- [ ] The workflow defines which inputs are trusted and which are untrusted.
- [ ] The workflow defines what evidence must exist before the action is allowed.
- [ ] The workflow defines whether a human confirmation step is mandatory.
- [ ] The workflow defines what happens when a required tool input is missing.

## While the tool runs
- [ ] The action is scoped to the minimum permission needed.
- [ ] The tool input is structured enough to validate automatically.
- [ ] The workflow records enough state to replay the action later.
- [ ] The workflow can distinguish tool failure from bad upstream reasoning.

## After the tool runs
- [ ] The workflow defines how success is verified.
- [ ] The workflow defines what should be shown to the user after success.
- [ ] The workflow defines what should happen after failure: retry, degrade, or escalate.
- [ ] The workflow does not allow silent failure to continue downstream.

## Operator review
- [ ] Another operator could understand this boundary without guessing.
- [ ] The workflow exposes one clear stop condition.
- [ ] The workflow exposes one clear escalation path.
- [ ] Repeated operator behavior has been marked for SOP or skill extraction.
