crackmapexec

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

Even without annotations, the description discloses the tool's active and potentially intrusive behavior: it exploits services, supports pass-the-hash/Kerberos, and executes modules like lsassy and mimikatz. It also states what output to expect. It does not fully detail side effects or authorization requirements, but it conveys enough behavioral context for an agent to treat it as an active exploitation 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 dense yet well-structured: identity and scope first, then capabilities, then usage guidance and alternatives, then output summary. Every sentence earns its place, and there is minimal filler for a tool with this breadth.

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 complex multi-protocol tool with 7 parameters and no output schema, the description is quite complete: it covers protocols, auth modes, modules, when to use it, alternatives, and expected output. It could add a brief note on required credentials or safety implications, but the core operational context is present.

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 100%, so the schema already documents all parameters. The description adds value by giving concrete module examples (lsassy, mimikatz, spider_plus) and highlighting pass-the-hash and Kerberos modes, which maps to ntlm_hash and opts. This goes beyond the baseline without fully replacing schema details.

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 identifies the tool as a pentesting Swiss-army knife for Windows/AD environments and names the specific protocols and actions it performs (enumerates/exploits SMB, WinRM, MSSQL, RDP, SSH, FTP; supports pass-the-hash and Kerberos). It also differentiates itself from siblings by positioning itself as the primary post-exploitation tool and explicitly calling out evil_winrm and enum4linux as alternatives.

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 gives explicit usage direction: use as the PRIMARY post-exploitation tool against Windows networks when you have credentials. It also provides clear when-not-to-use guidance by naming evil_winrm for interactive WinRM shells and enum4linux for detailed SMB enumeration.

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