nxc_enum

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

With no annotations, the description carries the full burden for behavioral disclosure. It mentions that passwords are 'redacted in logs', which is a useful transparency detail, but it does not state whether the tool is read-only, the network impact, authorization requirements, or potential side effects. The 'Returns' section focuses on output rather than behavioral traits.

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 concise and well-structured with an Args/Returns format. It avoids unnecessary verbiage and every line adds value. Slightly longer than necessary due to listing all parameters, but this is justified given the tool's complexity.

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?

The description covers purpose, parameters, and return values, which is fairly complete for a complex tool with 7 parameters. It lacks usage guidance and edge-case behavior, but the presence of an output schema (as noted in context) reduces the need for detailed return documentation. Overall it provides enough context for a capable 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?

The schema has 0% description coverage, so the description fully compensates by providing clear explanations for all 7 parameters: target, protocol, username, password, domain, modules, and timeout. It even includes example values and notes on optionality.

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 performs 'Enumerate network services and AD using NetExec', which is a specific verb+resource. It also distinguishes itself by referencing NetExec as the successor to CrackMapExec, differentiating it from other enumeration tools like enum4linux_scan and smbmap_scan.

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 explicit guidance on when to use this tool versus alternatives. While the description lists protocols and modules, it does not mention scenarios where nxc_enum is preferred over other AD/service enumeration tools. No exclusions or alternative tool names are provided.

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