Developer notes
Define the boundary before the endpoint.
Technical discussion material for evaluating a tool workflow. These notes describe design considerations, not a released SDK or a public API contract.
Begin with one operation
Specify the resource, accepted inputs, returned fields and caller. A customer-status lookup is a more useful first integration than unrestricted access to a customer database.
Make authority visible
Describe the permission required, who grants it, how it expires and when human approval is required. Keep resource credentials out of prompts and tool outputs.
Make failures testable
Include denied requests, expired credentials, timeouts and repeated execution in the acceptance criteria. Agree what evidence operators need to diagnose a failed call.
Bring a tool brief.
Use this worksheet to describe one operation, its permissions and its failure cases before an integration discussion.
Download the tool-scoping worksheetBring one concrete operation