Design observability for tool choice, tool arguments, and execution outcomes.

Instruction: Trace routing, policy, execution, and user-visible completion separately. Avoid recording secrets or full private payloads.

Context: Instrument an assistant so a correct API response cannot conceal a wrong tool choice or an incomplete user task.

Updated

Official answer available

Read the opening below, then unlock the full answer and practical guidance.

I would create a trace for the user task and child spans for routing, argument validation, policy evaluation, approval, execution, and result handling. Each event should carry a correlation ID and the relevant tool and schema versions. Sensitive values would be redacted or replaced with bounded metadata.

I would measure...

Your preparation path

Work through these questions in order. Read the answer aloud, then explain it in your own words.

Related Questions