Parallel Workflow

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

Annotations already indicate destructiveHint=true. The description does not elaborate on destructive behavior, side effects, or what constitutes 'execution' (e.g., state changes, resource creation). It adds minimal context beyond the annotation.

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, well-structured sentence that front-loads the purpose. No unnecessary words 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?

With no output schema, the description does not explain what the tool returns, error behaviors, or how results are communicated. Given three parameters and potential complexity, key contextual details are 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 coverage is 100%, with all parameters described. The description briefly gives examples for 'objective' (e.g., security audit) but does not add meaningful semantics beyond what the schema already provides for concurrency and timeout.

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 the tool executes a parallel multi-step subtask workflow for objectives like security audits, performance benchmarks, or repository inspections. It uses a specific verb ('execute') and resource ('workflow'), and provides concrete examples that distinguish it from planning-only sibling tools.

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 gives examples of when to use (e.g., security audit, performance benchmark) but does not explicitly state when not to use or suggest alternative tools. Sibling tools include many planning tools, but no guidance on choosing this over those is provided.

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