websex_ffuf

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: the container executes ffuf directly with argv tokens and never uses shell parsing, which tells the agent not to rely on shell expansion. It still omits destructive potential, rate/performance traits, and any permission context for what is inherently an active fuzzing tool.

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?

Three compact sentences with the execution model front-loaded and no filler; each sentence adds operational value. Slightly more could be trimmed only at the cost of the useful argv detail.

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?

An output schema exists so return values need not be described, and the execution model is covered. However, for a 4-param, zero-coverage active fuzzing wrapper with no annotations, the definition still lacks usage routing and a description of `stdin`, so it is only minimally complete.

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 compensate. It adds real meaning for three parameters by tying `arguments` to raw argv tokens, `working_directory` to relative engagement paths, and `engagement_id` to the namespace, but `stdin` is never explained, leaving one of four params undocumented anywhere.

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 names a specific verb and resource ("Run ffuf") and clarifies it is the WebSex wrapper, so the agent knows exactly which binary is invoked. It does not, however, distinguish this tool from near-neighbors like websex_wfuzz, websex_gobuster, or websex_feroxbuster, leaving sibling selection to the agent.

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 explains operational mechanics (relative paths, engagement namespace) but gives no guidance on when to choose ffuf over the many other web-fuzzing/directory-brute-force siblings. There is no when-to-use, when-not-to-use, or named alternative, so routing is left entirely to inference.

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