kali_dir_enum

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions using gobuster with the common wordlist, but does not explain what the tool actually does (e.g., sends HTTP requests), what the output looks like, or potential side effects such as being intrusive. This is a significant gap for a security scanning 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?

The description is one short sentence that is front-loaded with the action and purpose. Every word contributes to meaning, with no filler or repetition.

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?

With no output schema and no annotations, the description must explain what the tool returns or how results are presented. It does not do this. The tool is relatively simple, but the absence of return-value information and behavioral caveats makes it incomplete for an agent.

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 coverage is 100%, with both url and wordlist described in the input schema. The description adds minimal value by mentioning 'common wordlist', which is already reflected in the schema's default. Therefore, the baseline of 3 applies.

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 enumerates directories/files on a web server using gobuster, which is a specific verb+resource. This distinguishes it from sibling tools like kali_nmap (network scanning) and kali_web_scan (broader web scanning).

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 conveys a clear context: use this when you need to enumerate directories/files on a web server. It does not explicitly list alternatives or when-not-to-use, but the context is unambiguous enough for an agent to select it appropriately.

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