The most probable cause is incomplete transfer of relevant contextual information from the coordinating agent to the specialized sub-agents.
In a multi-agent architecture, each agent typically operates within its own execution context. Information established by the coordinator does not automatically become available to downstream agents unless the application explicitly transmits it.
The scenario provides a decisive diagnostic observation: individual sub-agents produce accurate results when they are manually supplied with the complete context.
This indicates that the agents possess the necessary capabilities but are operating with incomplete information during normal orchestration.
Option B therefore identifies the central failure.
The coordinator should provide each sub-agent with a structured context package containing the assigned task, relevant prior conclusions, applicable constraints, selected evidence, and important tool results.
This ensures that specialized agents interpret their assignments consistently with the broader workflow.
Option A suggests model randomness, but the scenario does not identify unstable dispatch instructions. Options C and D conflict with the confirmed retrieval-index configuration and successful isolated tests.
Databricks supports orchestrated multi-agent systems in which specialized agents are invoked through a coordinating component.
MLflow Tracing can record the inputs and outputs of each agent invocation, allowing engineers to inspect precisely which context was transferred and identify missing information at agent boundaries.
Official Databricks reference: Build a multi-agent system on Databricks Apps, Core concepts for agent observability, and Tracing AG2.
────────────────────────────────────────────────────
Submit