cos_dispatch_parallel_run

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

With no annotations, the description carries the full burden of behavioral disclosure. It discloses concurrency (asyncio.gather), a side effect (outputs persisted to the bundle), and ordering (list in input order). It does not cover error handling, timeouts, or rate limits, but these are not typically required for a dispatch tool of this type.

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 three sentences, front-loaded with the core action, and every sentence serves a purpose: action, usage trigger, and output behavior. There is no filler or redundancy.

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?

The tool has 8 parameters with zero schema descriptions, but the description provides a clear trigger condition and high-level behavior. Since an output schema exists, return values are well-defined externally. The main missing piece is parameter semantics; however, the trigger context (supervisor returns action='dispatch_parallel') may imply the agent already has the necessary values, making this a minimum viable but not complete description.

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 0%, so the description must compensate, but it provides no parameter guidance. There is no explanation of what formula_ids, session_id, task_marker, persona_id, model, intensity, timeout_s, or complexity mean or how they should be set. The description only indirectly references formula_ids via 'formula-agents' but does not clarify any parameter semantics.

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 starts with a specific verb and resource: 'Spawn multiple formula-agents concurrently via asyncio.gather.' It clearly distinguishes this from sibling dispatch tools by stating the unique parallel behavior and explicitly naming the alternative trigger ('Use when the supervisor returns action='dispatch_parallel'').

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 provides an explicit 'when to use' condition: when the supervisor returns action='dispatch_parallel' (e.g., security_auditor layers). This gives clear context for selection, but it does not explicitly mention when not to use it or list alternative tools, so it falls short of the highest bar.

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