A tool should execute only while its prerequisites still hold. Collecting the right information earlier in the call is insufficient if availability, permission, or the caller’s intent changes before the write.
Prerequisites describe executable state
A prerequisite is a condition that must be satisfied for a particular action. For booking, examples include a resolved service, an eligible location, a specific time, current capacity, and the required confirmation. Different tools require different sets.
In a proposed execution service, define prerequisites as backend checks with explicit failure categories. Some checks can happen during intake to improve the conversation. Recheck conditions that can change at the final write boundary, using the authoritative system’s concurrency controls where available.
Do not confuse a prerequisite with a conversational preference. A caller’s preferred employee may guide a search; a verified right to modify an appointment governs whether the write is permitted. Both matter, but they should not share one vague “ready” flag.
Work through a fictional repair booking
A caller wants a furnace repair tomorrow. The assistant collects a service address and sees an available morning slot. Before execution, the system must confirm that the address is covered, the requested service is supported, and capacity remains available for the required duration.
If another caller takes the slot during readback, the final booking should fail with an availability result and offer new options. It should not proceed because the assistant remembers saying the time was available a minute earlier.
| Prerequisite failure | Expected recovery |
|---|---|
| Address outside service area | Explain the supported boundary |
| Caller has not confirmed | Ask for confirmation before writing |
| Slot no longer available | Present newly checked alternatives |
| Identity verification expired | Follow the defined re-verification path |
| Service duration changed | Recalculate resource availability |
Test that each failure prevents the write. Also test that fixing one missing prerequisite does not erase another unresolved condition. A valid address alone should not convert an unconfirmed request into a confirmed booking.
Avoid expensive checks without weakening correctness
Checking every dependency after every spoken word increases latency and downstream load. Cache stable facts appropriately, but keep time-sensitive decisions close to execution. Mark cached observations with their source and age so they are not mistaken for fresh authority.
A prerequisite chain can become difficult to explain when many conditions fail simultaneously. Return the safest useful next question and retain the full diagnostic detail for authorised review. The conversation should progress without exposing internal policy logic unnecessarily.
This design is proposed. The HVAC workflow case study documents service-area checks and confirmation for service requests, not calendar booking. See argument validation for the complementary input boundary.
Tool prerequisite FAQ
Can an earlier availability lookup authorise a later booking?
No. The final write must enforce the current capacity rule.
Should prerequisites live only in the prompt?
No. The execution service must enforce the conditions relevant to the action.
What if several prerequisites fail?
Choose a clear recovery sequence, keep unresolved conditions visible, and execute only after every required condition is satisfied.