Delegate a task to a DeepSeek subagent

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must fully inform about behavior. It only mentions launching/resuming and subagent types, but lacks details on side effects, authentication, resource usage, or what happens if a session fails. Insufficient for a tool that creates child processes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences long, front-loaded with the core action, and includes essential usage guidance without any filler. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 9 parameters, no output schema, and no annotations, the description is too brief. It does not cover return values, error scenarios, or constraints, making it incomplete for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, and the description only implicitly references subagentType and taskId. It does not explain parameters like cwd, prompt, maxTurns, allowedPaths, contextFiles, or runVerification, leaving the agent to infer usage from names alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it launches or resumes a DeepSeek child session for complex tasks. It distinguishes between repo-scout (read-only) and implementer (code changes) subagent types, and mentions using taskId for continuation, making its purpose specific and distinct.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly provides guidance on when to use each subagent type and how to continue a task via taskId. However, it does not discuss when not to use the tool or provide comparisons with the sibling tool delegate_execute.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.