scan_fuzzing_ffuf

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It conveys that the tool performs fast ffuf-based fuzzing and is flexible, but it does not disclose side effects, network impact, preconditions, or output behavior. The schema's evasion parameter adds some behavioral context, but the description itself is thin on these details.

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 two sentences, front-loaded with the core purpose, and contains no redundant restatement of the schema. Every clause adds useful context: tool identity, speed/flexibility comparison, and supported fuzzing targets.

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 output schema exists and the input schema covers all parameters with rich descriptions, the tool definition is mostly complete. The description covers the main supported use cases and distinguishes from gobuster, though it could be slightly more explicit about usage conditions and behavioral caveats for a fuller picture.

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%, and each parameter is documented with defaults and helpful notes such as the FUZZ placeholder behavior. The description adds little parameter-level meaning beyond the schema, so the baseline score of 3 is appropriate.

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 opens with a specific action, 'Fuzzing rápido usando ffuf', and immediately clarifies scope: directory fuzzing, GET/POST parameter fuzzing, and REST API endpoints. It also distinguishes itself from the sibling gobuster tool by claiming to be faster and more flexible, making the tool's purpose and differentiation clear.

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 provides clear context by listing supported fuzzing types and explicitly comparing itself to gobuster ('Mais veloz e flexível que gobuster'). It does not explicitly state when not to use it or name all alternative tools, but the context is sufficient for an agent to decide when this tool is appropriate.

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