spawn_subagent

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

No annotations are provided, so the description must fully disclose behavior. It states each role has 'customized prompts, tools, and behavior' but gives no details on side effects, resource usage, concurrency, or error handling. The 'write_files' parameter hints at file writing, but the overall behavioral impact is vague.

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 a single, front-loaded sentence that states the core purpose and lists key elements. It is concise with no wasted words, earning every bit of its length.

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's complexity (7 parameters, enums, nested objects, no output schema), the description is too brief. It does not explain return values, error handling, subagent lifecycle, or how to use results. Important context like default behaviors and limitations is missing.

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 description coverage is 100% with detailed parameter descriptions (e.g., role enum with inline explanations). The description adds value by grouping roles and mentioning customized behavior, but the schema already explains each parameter well, so the description does not significantly enhance parameter understanding.

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 'Spawn specialized AI subagent' and lists predefined roles, making the purpose immediately clear. It distinguishes from sibling tools like 'council' or 'parallel_agents' by focusing on role-specific customization.

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 mentions roles and their purpose (e.g., 'code-reviewer (quality review)') but does not provide explicit guidance on when to use this tool over alternatives. It implies usage through role enumeration but lacks direct comparisons or exclusions.

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