mimikatz_sekurlsa_msv

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 states that credentials are extracted but does not disclose required privileges, potential side effects, whether the operation is read-only, or security/AV implications. For a sensitive Mimikatz operation, this is a significant transparency 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 a single, front-loaded sentence with no filler or redundancy. Every word contributes meaning: 'Extract' states the action, 'MSV1_0 credentials' states the resource, and '(NTLM hashes)' clarifies the output type.

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 tool is contextually complex: it interacts with LSASS memory, likely requires high privileges, returns credential material, and has many closely related sibling tools. With no output schema and no annotations, the description should at least note prerequisites or expected output shape. It only gives a one-line action, leaving the agent without key operational context.

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 input schema has zero parameters and 100% coverage, so there is nothing for the description to explain about parameters. The description adds value by clarifying what the tool produces, but no parameter-specific documentation is needed.

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 names a specific verb ('Extract') and a precise resource ('MSV1_0 credentials'), with a clarifying parenthetical ('NTLM hashes') that indicates the expected result type. This is clear and helps distinguish the tool from wdigest or kerberos siblings, but it does not address overlap with sekurlsa_logonpasswords, so sibling differentiation is incomplete.

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 when-to-use guidance is provided beyond the inherent implication of the action itself. The description does not mention when to prefer this over sekurlsa_logonpasswords, how it relates to the other sekurlsa tools, or any prerequisites such as elevated/system privileges.

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