The frameworks that orchestrate agents well share one rule: every agent gets one clear role and a defined handoff. A role that's vague ("help with the project") produces a vague agent; a role that's specific ("extract the three most-cited claims and pass them on") produces a useful one. The handoff is the other half — the exact moment and format one agent passes work to the next.
Bad orchestration is a pile of agents all doing a bit of everything, stepping on each other. Good orchestration reads like a relay: clear baton, clear exchange zone. The specificity of the handoff matters as much as the specificity of the role — "pass the draft" is weaker than "pass the draft with the three claims flagged and sources attached."
Run the seed: define two agent roles and the exact handoff between them — what the first produces, in what shape, that the second needs to start.