enumerate_directories

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

With no annotations provided, the description must fully convey behavioral traits. It fails to disclose whether the enumeration is passive or active, potential safety risks, required permissions, or output format, leaving the agent without necessary context.

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 single sentence is extremely concise but lacks structure or additional details. While brevity is valued, this under-specification undermines the description's effectiveness; it does not earn its place by providing sufficient 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 that the tool has two parameters, no output schema, and no annotations, the description should compensate but offers almost no context. The agent cannot determine how to use the parameters or what the tool returns, making it incomplete for operational use.

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 for both parameters. It does not explain that 'wordlist' is a file path or 'target_url' format. No parameter details are provided, making it inadequate.

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 action ('Enumerate directories') and the target ('on a web target'), providing a specific verb+resource. It is distinguishable from sibling tools like 'scan_website_comprehensive' or 'scan_ports', but the description does not explicitly differentiate it.

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 versus alternatives such as 'scan_website_comprehensive' or 'crawl_spa'. The description only implies usage through its name, lacking any explicit context or exclusions.

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