Choose work that can be separated cleanly
A good subtask has a focused question, a concrete output, and a clear boundary. For example, one subagent might gather evidence about a specific topic while the main agent compares findings and prepares the final response. Avoid dividing work that depends on constant coordination or shared edits to the same files unless the responsibilities are carefully separated.
Give the subagent enough background to understand the goal, the sources it may use, and the format of the result. State what it should report and what it should leave for the parent agent. This makes its contribution easier to evaluate and reduces the chance that two agents repeat the same work.
Review the delegated result before relying on it
A subagent's output is material for the main agent to inspect, not an automatic approval of the work. Check important facts against the cited evidence, review any files or actions it produced, and decide whether its findings fit the larger request. A concise handoff should distinguish verified observations from open questions.
If the subtask requires access to tools or data, provide only what it needs. Do not assume it can reach the parent agent's local files, connected storage, or private context unless those are explicitly included. Clear boundaries, limited tools, and a review of the handoff make delegation more predictable.