Squad Run

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

Despite no annotations, the description comprehensively discloses behavioral traits: pipeline stages, gates (Implementation Gate, Human Gates, notification approval contract), mode behavior, and that it returns Coordinator persona, matched routing, and dispatch request. No hidden behaviors or contradictions.

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 well-structured and informative but slightly long. Every sentence adds value, starting with the core purpose, then pipeline details, then mode options, then output, and finally usage guidance. No unnecessary repetition.

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 complexity (7 parameters, no output schema, multiple siblings), the description covers all essential aspects: purpose, behavioral pipeline, mode differentiation, parameter context, and sibling differentiation. It adequately prepares an AI agent to select and invoke the tool correctly.

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 100%, so baseline is 3. The description adds extra semantic value beyond the schema by explaining mode options ('bounded validator loop', 'full gated pipeline') and the role of the request parameter ('any intent; the Coordinator classifies it'). While not exhaustive for all 7 parameters, it enhances understanding for key ones.

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 runs the full squad pipeline for any request, describes the pipeline stages (Research -> Plan -> Implement -> Review), and explicitly distinguishes it from narrower sibling tools by saying 'Use when no narrower squad_* tool fits, or for end-to-end work.'

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?

Provides explicit guidance on when to use this tool (catch-all, end-to-end work), describes different modes (autonomous, autopilot) with their effects, and mentions delegated execution. No ambiguous or missing usage context.

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