aflpp.stop_fuzz

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

The description discloses specific behavioral details: it sends SIGTERM followed by SIGKILL. This goes beyond a generic 'stop' and alerts the agent to the forceful termination nature. It does not mention permissions or error scenarios, but the signal sequence is valuable transparency for a mutation-like operation with no annotations.

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 sentence with no wasted words. It front-loads the action and includes the key behavioral detail in parentheses. Every word contributes to the meaning.

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 simplicity of the tool, the description covers the core purpose and a key behavioral trait, but it leaves gaps: the PID/job_name mismatch is unexplained, parameters are undocumented, and the return value is not described. While not a complex tool, the description is not fully sufficient for an agent to invoke it correctly without additional inference.

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 does not explain the workspace or job_name parameters. It also introduces the term 'PID' which does not correspond to any schema parameter, adding confusion rather than clarifying the input semantics. The description fails to compensate for the missing schema documentation.

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 action (stop) and the resource (running afl-fuzz job), and distinguishes it from siblings like start_fuzz. However, the phrase 'by PID' is inconsistent with the schema's actual parameter 'job_name', which could confuse an agent about how the job is identified.

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 implies usage for stopping a running fuzzing job, which is obvious from the tool name and context, but it does not explicitly specify when to use it versus other tools or exclude any cases. No alternatives are mentioned, but for a stop operation this is reasonably inferable.

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