What information should the orchestrator validate before executing a tool call?

Example Answer

The way I'd think about it is this: The orchestrator should validate identity, permissions, schema compliance, argument completeness, business-policy constraints, and whether the requested action is appropriate for the current workflow state. Syntax is only the first layer.

I also want validation on reversibility and approval requirements for risky actions. Some calls are valid JSON and still should not execute because the user context changed, authorization expired, or the action no longer makes sense in the workflow.

The orchestrator is the control plane. If it only checks schema shape, it is not doing enough to protect the system from model mistakes.

What matters in an interview is not only knowing the definition, but being able to connect it back to how it changes modeling, evaluation, or deployment decisions in practice.

Common Poor Answer

A weak answer is saying the orchestrator should validate that the JSON matches the schema. That is necessary, but not close to sufficient.