ffuf_fuzz

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains the required FUZZ placeholder and automatic appending, how filter/match codes work, and default thread/rate behavior. It does not mention potential side effects like high request volume or authorization requirements, but it provides substantial operational detail.

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 well-structured with a clear opening summary, an Args section that explains each parameter, and a Returns section. It uses bullet-like formatting and front-loads the core purpose. Every sentence adds value and nothing is redundant.

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 tool's complexity (10 parameters, no schema descriptions, no annotations), the description is thorough. It covers the FUZZ substitution rule, parameter semantics, defaults, and return values, making the tool fully understandable without needing to inspect the schema or output format.

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?

The schema provides zero description coverage, but the description compensates fully by listing and explaining every parameter in the Args section, including url, wordlist, method, filter_codes, match_codes, extensions, threads, rate, headers, and timeout. This far exceeds the schema's bare structure.

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 'Fuzz directories, files, and endpoints using FFUF' with a specific verb and resource. It distinguishes itself by naming FFUF, but does not explicitly contrast with similar sibling tools like gobuster_scan or feroxbuster_scan, so it lacks direct sibling differentiation.

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 for when to use the tool: 'discover hidden files, directories, APIs, and endpoints that are not linked from the application's public pages.' It does not explicitly mention alternatives or when not to use it, but the use case is unambiguous.

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