aflpp.start_fuzz_cluster

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether the tool blocks or returns immediately, whether it spawns background processes, modifies the workspace, requires pre-existing corpus/campaign directories, or is destructive. The phrase 'master + secondary' gives a small hint about process architecture, but side effects and lifecycle are entirely undisclosed.

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 with no fluff, which is efficient. However, for a tool with this complexity (9 parameters, nested options, instance overrides), one sentence is under-specified. It is not just concise; it omits essential context, so it does not fully earn its place as an adequate tool description.

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 high complexity (multiple required parameters, nested objects, no output schema, no annotations), this description is severely incomplete. It does not explain what a 'campaign' entails, how master/secondary instances are configured, any preconditions (like an initialized workspace or corpus), or what the return value/behavior after starting might be. The description offers only the bare minimum of context.

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% and the description makes no mention of any parameters. With 9 parameters (including required ones like workspace, campaign_name, instances, target_cmd, corpus_name), the description must compensate for the schema's lack of textual explanations, but it does not. The agent gets no help understanding what each parameter means or how they relate.

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 uses a specific verb ('Start') and identifies the exact resource ('multi-instance afl-fuzz campaign') with a clarifying parenthetical ('master + secondary instances'). This distinguishes it from sibling tools like aflpp.start_fuzz, which presumably starts a single instance, and aflpp.suggest_fuzz_cluster_mix, which is advisory. It clearly states what the tool does.

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 does not provide any explicit guidance on when to use this tool versus alternatives. There is no mention of 'use this instead of start_fuzz when you need parallel fuzzing' or any exclusion criteria. The only implied usage is 'multi-instance', which suggests it is for parallel campaigns, but no alternatives are named or contrasted.

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