docs(workflows): clarify delegation tool naming and task completion behavior in collaboration examples (#1935)

Co-authored-by: Kristopher Overholt <koverholt@google.com>

Author: itsatefe

docs/workflows/collaboration.md

@@ -59,7 +59,8 @@ a small team of subagents and assign them to a coordinator agent:
     root = Agent(
         name="travel_planner",      # coordinator agent
         sub_agents=[weather_agent, flight_agent],
-        # Auto-injects: request_task_weather_checker, request_task_flight_booker
+        # Auto-injects delegation tools named after each subagent:
+        # weather_checker, flight_booker
     )
     ```
 
@@ -68,7 +69,8 @@ a small team of subagents and assign them to a coordinator agent:
     In ADK Go v2.0.0, the `Mode` field on `llmagent.Config` accepts the same
     mode strings as Python: `"chat"`, `"task"`, and `"single_turn"`. Declaring
     `SubAgents` on the coordinator agent causes ADK to automatically generate
-    `request_task_<name>` delegation tools, exactly as in Python.
+    a delegation tool for each subagent, named after the subagent itself,
+    exactly as in Python.
 
     ```go
     --8<-- "examples/go/snippets/workflows/collaboration/main.go:get-started"
@@ -130,7 +132,7 @@ each mode:
     <tr>
       <td><strong>Return to parent</strong></td>
       <td>Manual (via transfer)</td>
-      <td>Automatic (via <code>complete_task</code>)</td>
+      <td>Automatic (via <code>finish_task</code>)</td>
       <td>Automatic (with result)</td>
     </tr>
   </tbody>
@@ -160,11 +162,11 @@ automatically advances to the next node based on the logic of the workflow
 agent's graph.
 
 **As a transferee from an LlmAgent:** When a parent ***LlmAgent*** transfers
-control to a task agent via `request_task`, the task agent executes until it
-calls `complete_task`. At that point, control automatically returns to the
-originating agent that initiated the transfer. This behavior differs from
-default, chat ***mode*** agents, which require explicit `transfer_to_agent`
-calls to hand back control.
+control to a task agent via the delegation tool named after that subagent, the
+task agent executes until it calls `finish_task`. At that point, control
+automatically returns to the originating agent that initiated the transfer.
+This behavior differs from default, chat ***mode*** agents, which require
+explicit `transfer_to_agent` calls to hand back control.
 
 <table>
   <thead>

examples/go/snippets/workflows/collaboration/main.go

@@ -25,12 +25,13 @@
 //   - "chat" (ModeChat, default): full user interaction; agent controls
 //     flow until it explicitly calls transfer_to_agent.
 //   - "task" (ModeTask): agent may ask the user clarifying questions and
-//     automatically returns control to the parent when it calls complete_task.
+//     automatically returns control to the parent when it calls finish_task.
 //   - "single_turn" (ModeSingleTurn): no user interaction; executes one turn
 //     and returns automatically; can run in parallel with peer agents.
 //
 // When a coordinator llmagent declares SubAgents, ADK automatically generates
-// request_task_<name> tools for each subagent, wiring the delegation pattern.
+// a delegation tool for each subagent, named after the subagent itself,
+// wiring the delegation pattern.
 //
 // When an llmagent is used as a node in the v2 workflow graph engine
 // (workflow.NewAgentNode), the engine automatically applies ModeSingleTurn
@@ -130,8 +131,8 @@ func newCollaborativeTeam(ctx context.Context) (agent.Agent, error) {
 	}
 
 	// The coordinator agent declares SubAgents. ADK automatically generates
-	// request_task_weather_checker and request_task_flight_booker tools so the
-	// coordinator can delegate work to each subagent.
+	// weather_checker and flight_booker delegation tools, named after each
+	// subagent, so the coordinator can delegate work to each one.
 	return llmagent.New(llmagent.Config{
 		Name:        "travel_planner",
 		Model:       model,