A parcel enrichment coordinator must run extract_parcel_metadata before any enrichment tools. How can it enforce that first call?
Select an answer to reveal the explanation.
Short Explanation
Need parcel metadata before enrichment? Don't just wish—force the named extract tool with tool_choice on that first turn.
Full Explanation
A parcel enrichment coordinator that must run extract_parcel_metadata before any enrichment tools should use tool_choice to force the named extract_parcel_metadata tool on the first turn. Programmatic forced choice enforces prerequisite order when later enrichment depends on parcel identifiers and attributes that do not yet exist in context.
Named tool_choice works because prompt-only ordering is probabilistic. Municipal parcel pipelines need a hard first step: extract metadata, then enrich. Forcing the extractor removes the chance the model jumps straight to enrichment with missing keys.
Hoping the system prompt alone always orders tools correctly with no enforcement fails under prompt pressure and long contexts. Removing extract_parcel_metadata from the tool list entirely makes the required first call impossible. Setting tool_choice to forbid all tools including extraction blocks the prerequisite and stalls enrichment.
Exam caveat: after the forced first call succeeds, relax tool_choice so subsequent enrichment tools can be selected normally. Operational check: on turn one, assert the only tool call is extract_parcel_metadata; on later turns, confirm enrichment tools run using extracted fields.