aflpp.start_fuzz

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

With no annotations, description must disclose side effects and behavior. It only reveals 'non-blocking', but omits what starting a job entails (e.g., process creation, filesystem changes, persistence, error handling, resource consumption), leaving the agent blind to significant mutating behavior.

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?

One clear, front-loaded sentence with no filler earns high marks for brevity and structure. However, given the tool's complexity, the extreme brevity borders on under-specification, but it remains appropriately concise for a starting point.

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?

For a 22-parameter asynchronous job launcher with no output schema and no annotations, the description provides almost no contextual completeness: no prerequisites, no return/status info, no param semantics, no relationship to cluster or stop/status tools. The agent cannot safely invoke this tool based on the description alone.

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?

Input schema has 22 parameters with 0% description coverage, and the description mentions none of them. Required fields like job_name, target_cmd, and corpus_name are not explained, nor are the many optional env/settings parameters, so the agent must infer meaning from raw schema names only.

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?

Description uses specific verb 'Start' and identifies resource 'an afl-fuzz job in the workspace', with 'non-blocking' clarifying execution mode. This clearly distinguishes it from sibling start_fuzz_cluster (cluster) and lifecycle tools like stop_fuzz/status.

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?

No guidance on when to use this over start_fuzz_cluster or prerequisites like initialized workspace, existing corpus, or instrumented target. Single sentence provides no usage context beyond location.

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