enum4linux

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

No annotations are provided, so the description carries the full burden. It discloses that the tool operates without authentication, mentions RID-cycled user lists, and describes output structure. While it doesn't mention potential side effects like detection or service disruption, it accurately conveys the tool's read-only enumeration nature, which is sufficient for a recon 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 extremely concise, two sentences total, with the core purpose front-loaded. It avoids any redundant or filler content, and every sentence contributes to understanding the tool's scope and usage.

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?

For a tool with only two parameters and no output schema, the description is remarkably complete. It specifies the target protocols (SMB, ports 139/445), mentions the output type (structured enumeration data), and provides usage guidance. No critical information is missing for an agent to correctly select and invoke this tool.

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?

The schema already describes both parameters with 100% coverage, so the baseline is 3. The description adds value by providing an example usage of the opts parameter ('-a' for all enumeration), which helps the agent understand how to use it beyond the schema's bare description. This extra context justifies a score above baseline.

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's function as a Windows/Samba enumeration tool, lists specific data types extracted (user lists, shares, groups, password policies, OS info), and explicitly distinguishes it from more advanced tools like crackmapexec and impacket. This provides a clear, specific verb-resource pair and differentiates from siblings.

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 explicitly states when to use this tool ('Windows domain reconnaissance without authentication') and when not to (when credentials are available, use crackmapexec or impacket). This gives clear direction on tool selection, leaving no ambiguity for the agent.

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