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

With no annotations, the description carries the full burden of behavioral disclosure. It does not state whether the tool performs a network request, whether it is safe/non-destructive, what it returns, or any side effects. The phrase 'Open directory-index exposure' implies a check, but the behavior is opaque. No annotation contradiction exists, but the lack of behavioral context is a significant gap.

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 very short, which is concise, but it is under-specified rather than efficiently informative. The title 'Dirlisting' and description are nearly redundant, and the description does not earn its place by adding meaningful detail. It is not poorly structured, but it is too sparse to be effective.

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 the tool's apparent purpose (checking for directory listing exposure), the description is incomplete. It lacks input format, output expectations, and any operational context. The output schema exists but is not shown in the provided data, so the description should compensate. The single parameter is undocumented, and no usage context is provided, making this inadequate for an agent to invoke correctly.

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%, and the only parameter 'q' has no description. The tool description does not explain what 'q' represents (target URL? domain? IP?). The default empty string is unexplained. The description adds no meaning beyond the schema, and the schema itself is unhelpful, so the agent cannot infer how to populate the parameter.

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 'Directory Listing: Open directory-index exposure (per-target)' states a resource and a general action, but the verb is weak and the phrasing is ambiguous. It does not clearly distinguish this from sibling tools like 's3buckets', 'gitexposed', or 'hostsearch' that also probe for exposed content. The term 'Open directory-index exposure' is jargon-heavy and does not specify what the tool actually does (e.g., checks for open directory listings on a target URL).

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. The description does not mention prerequisites (e.g., a URL vs a domain), what kind of target is expected, or when this tool is preferable to related exposure-checking tools. The 'per-target' hint is the only contextual clue, which is insufficient.

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