api_ffuf_fuzz

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention potential destructiveness (ffuf can be aggressive), rate limiting, or that it runs on a Kali server. The parameter 'mc' defaults to 200,301,302,403 but the description doesn't clarify impact.

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 concise, using a clear list format for parameters. It front-loads the main purpose in the first sentence. However, the list might be too terse, lacking example usage or more detailed context.

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 an output schema (not shown), so return values are covered. However, the description lacks context about prerequisites, potential side effects, or how the tool fits into a workflow. It is adequate but not comprehensive.

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%, so the description must add meaning. It provides brief explanations for each parameter (e.g., 'Match HTTP status codes (comma-separated)' for mc). However, explanations are terse and incomplete (e.g., headers format not fully specified).

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 the tool uses ffuf for content discovery and parameter brute-forcing, with a specific example of URL format. It distinguishes itself from sibling fuzz tools like api_fuzz_endpoint and api_kiterunner_scan by naming ffuf explicitly.

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 this tool versus other fuzzing tools (e.g., api_fuzz_endpoint, api_kiterunner_scan) or under what conditions (e.g., target scope, authentication). It only lists arguments without context.

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