Tool Registry Planning Template
Give agentic workflows a deterministic operating layer so tools carry state, permissions, validation, execution, and evidence.
Fill this onlineTemplate preview
The exact sections inside the download.
Read tool
What state can the system retrieve safely?
Write tool
What state can the system change, create, send, or assign?
Validation
What schema, permission, or business rule must pass first?
Approval
Which actions need human approval before execution?
Receipt
What result proves the tool completed correctly?
Tool owner
Who owns each tool contract and its failure behavior?
01 / 03
Frame the decision
Name the real operating need before designing a solution.
Name the workflow this registry enables.
CRM, inbox, database, calendar, documents, analytics, or internal tools.
Name the action that most needs approval, validation, or fallback.
How to use it
Start with one real decision.
Complete the canvas with the workflow owner, then use the blank areas to expose missing context and controls.