Tools and their safe contracts
Words made simple
A few useful meanings before you read the explanation.
- Retrieval
- Finding and fetching information that is useful for the current question.
- Durable
- Able to retain progress and recover across interruptions. Durable workflows require appropriate storage and retry behavior.
- Idempotency
- Making a repeated request have the same intended business effect as one request. It helps avoid duplicate submissions or payments.
More words from this lesson
- Tenant
- A customer or organization whose data must stay separate from other customers in a shared application.
| Tool | Arguments from model | Trusted server context/checks | Minimal result | Failure behavior |
|---|---|---|---|---|
| Customer lookup | Customer reference if needed | Tenant, caller, permitted customer relationship | Permitted display/profile fields | Deny access without leaking existence |
| Policy lookup | Policy ID or safe selector | Ownership, validity, allowed product/region | Policy/version IDs and permitted summary fields | Clarify selector or return unavailable |
| Claim status | Claim ID | Tenant, policy/customer ownership, read scope | Status code, safe reason, required-doc types | Denied, not found under safe policy, or transient unavailable |
| Create claim | Approved draft reference | Exact approval, current rules, idempotency key | Claim ID and durable receipt | Reject invalid draft; reconcile unknown commit |
| Email draft/send | Draft ID / permitted recipient selection | Role, consent, recipient/attachment/content checks, send approval | Draft or message receipt | No send on invalid approval; reconcile uncertain send |
| Document search | Bounded query | Tenant, document ACLs, policy/version/date filters | Bounded excerpts and source IDs | No evidence versus retrieval failure kept distinct |
- Never accept a model's
customerIdas proof of the current customer. - Never let the model supply an unrestricted email URL, SQL query, database filter, or role field.
Can you explain it without the notes?
Tools and their safe contracts
Use your own words. Explain an example and one limitation before checking the explanation.
Check your explanation
Never accept a model's customerId as proof of the current customer. Never let the model supply an unrestricted email URL, SQL query, database filter, or role field.
Turn this concept into a clear answer.
Practice this conceptAdapted from 13_AI.MD · “Tools and their safe contracts”. Examples are study fragments; framework behavior can depend on your version.