tools_ffuf

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It only states that FFUF is executed, offering no information about network activity, potential impact, output format, or safety considerations. This is nearly identical to a stub and fails to disclose any meaningful behavior.

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 extremely short, but this is under-specification rather than effective conciseness. It front-loads the main action but omits crucial context that would make the tool usable. The single sentence does not earn its place because it provides almost no useful 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 the tool's complexity (5 parameters, no output schema, no annotations), the description is completely inadequate. It does not mention required parameters, return values, execution context, or how to interpret results, making it nearly useless for an agent attempting to invoke it correctly.

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 provides no parameter details. While parameter names like 'url' and 'wordlist' are somewhat self-explanatory, there is no explanation of expected formats, defaults, or how 'additional_args' should be used. The description fails to compensate for the lack of schema descriptions.

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 'Execute FFUF web fuzzer' identifies the specific tool (FFUF) and its general purpose (web fuzzing), which distinguishes it from sibling tools like nmap or gobuster. However, it does not elaborate on what fuzzing entails or the tool's typical use case, so it is clear but not fully differentiated.

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?

No guidance is provided on when to use this tool over alternatives like gobuster, dirb, or api_ffuf_fuzz. The description gives no context for appropriate scenarios, prerequisites, or exclusions, leaving the agent to infer usage from the tool name alone.

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