mimikatz_sekurlsa_wdigest

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

No annotations are present, so the description carries the full burden. It says credentials are extracted from LSASS memory but does not disclose the elevated privileges typically required, the sensitive/permission-sensitive nature of the operation, or any risks or side effects.

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 a single efficient sentence with no filler. The action and target are front-loaded, making it easy for an agent to parse quickly.

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 sensitive credential-extraction tool with no annotations, output schema, or parameters, the description is too minimal. It omits operational context such as prerequisites, expected output, and how it relates to other Mimikatz credential-extraction functions.

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 tool has zero parameters and an empty schema, so there is no parameter detail the description needs to add. The baseline of 4 for no-parameter tools applies.

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 a specific verb and resource: extract WDigest credentials from LSASS memory. The WDigest naming distinguishes it from sibling tools targeting other credential types or functions like msv, kerberos, or logonpasswords.

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 about when to use this tool versus siblings such as mimikatz_sekurlsa_logonpasswords or mimikatz_sekurlsa_msv. The description does not mention broader alternatives or conditions that would make WDigest the right choice.

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