ffuf

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

No annotations are provided, so the description must carry the full burden. It only mentions speed ('fast') but does not disclose network behavior, ethical implications (though 'consent' parameter hints), authorization needs, or the fact that it can perform vhost fuzzing beyond directory/file discovery.

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 and adequately concise. However, it lacks structure and does not provide a clear breakdown of features. It is not verbose, but the conciseness comes at the cost of missing critical information.

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 four parameters including an enum with three modes (dirs, files, vhosts) and a consent boolean, the description is incomplete. It does not cover the vhost mode, explain the session_id parameter, or describe what the tool does in detail. With no output schema, the agent has no understanding of return values.

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%, meaning the schema provides no property descriptions. The tool description does not explain any parameter: 'url', 'session_id', 'mode', or 'consent'. It adds no semantic value beyond the schema types and enum.

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 'Fast web fuzzer for directory/file discovery' clearly identifies the tool's purpose as discovering directories and files through fuzzing. It distinguishes it from general scanners like nmap or sqlmap, but does not explicitly differentiate it from sibling tools like gobuster or wfuzz that serve similar roles.

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 no guidance on when to use ffuf versus alternative tools, no prerequisites, and no usage context. With siblings like gobuster and wfuzz available, the lack of usage guidelines makes it harder for an agent to select the right tool.

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