websex_dirb

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

With no annotations, the description carries the full behavioral burden, and it does disclose meaningful execution semantics: raw argv tokens with no shell parsing (an injection-relevant trait) and execution from the selected engagement namespace. It omits permissions, resource limits, expected runtime, and output shape, so the disclosure is partial rather than complete.

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 tight sentences with no filler, and the core action plus execution model are front-loaded ahead of the namespace/path caveat. It is appropriately sized, though it spends a sentence on the toolkit framing rather than differentiating the tool.

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. But for a 4-parameter, annotation-free tool sitting among many near-identical scanners, the absence of selection guidance and of `stdin` semantics leaves real gaps.

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% across 4 parameters, so the description must compensate. It explains `arguments` as argv tokens and `working_directory` via the relative-path convention, and implies `engagement_id` selects the namespace, but leaves `stdin` completely unexplained and gives no format examples for the argv array.

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 dirb') and clarifies it executes the well-known directory brute-forcer via argv tokens. It does not, however, distinguish this from the many sibling content-discovery tools (gobuster, ffuf, feroxbuster, dirsearch, wfuzz), so an agent cannot tell from the text alone when dirb is the right pick.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative, despite ~5 direct siblings in the same directory-brute-force category. The engagement-relative-path note is a usage constraint, not a routing rule, so the agent is left to infer selection entirely.

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