ffuf_fuzz

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that execution happens on a remote Kali machine, but says nothing about request volume/rate, detectability, runtime, permissions on the Kali host, or how results are surfaced for a high-volume active fuzzing operation.

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?

Two tight sentences: the first front-loads what the tool is and where it runs, the second explains the FUZZ injection marker and the main use cases. 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?

There is no output schema and no annotations, and the description does not explain result format, where output lands, or runtime expectations for a 7-parameter active scanning tool. It is adequate for purpose and the FUZZ mechanic but leaves the agent guessing about results and operational side effects.

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 100%, so the baseline is 3; every parameter is already documented with examples in the schema. The description adds only a mild note that FUZZ can also be placed in 'headers', which has no corresponding schema parameter, so it adds little usable meaning.

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?

States a specific verb and resource ('Run ffuf web fuzzer against a target URL') plus the distinctive FUZZ-keyword mechanism, so the agent knows exactly what it does. It does not differentiate itself from the closely related sibling gobuster_scan, which also does directory discovery, so it stops short of a 5.

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?

'Useful for directory discovery, parameter fuzzing, and virtual host enumeration' gives implied usage contexts but never says when to choose this over gobuster_scan, nmap_scan, or sqlmap_scan, and offers no exclusions or prerequisites. Coverage is implied rather than explicit.

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