mimikatz_lsadump_sam

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

No annotations are provided, and the description adds little beyond the one-line summary. It does not disclose privilege requirements, whether the operation is read-only, what output format to expect, or that offline hive paths are supported.

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 one short, front-loaded sentence with no filler. The action, target, and scope are all clear in seven words, making it appropriately concise for a tool with such a simple purpose.

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 no annotations, no output schema, and two optional offline-analysis parameters, this description is too sparse. It does not explain live versus offline operation, required privileges, or how to pick it over related mimikatz tools. The one-liner is insufficient for confident invocation in varied scenarios.

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 covers 100% of parameters with clear descriptions for sam_hive and system_hive, so the baseline is 3. The description adds no extra parameter meaning, but no compensation is needed since the schema already carries that weight.

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 states a specific action ('Dump'), a specific resource ('SAM database hashes'), and clarifies the scope ('local accounts'). This makes it immediately distinct from siblings like mimikatz_lsadump_dcsync (domain hashes) and mimikatz_lsadump_secrets.

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 given on when to use this tool versus alternatives. It does not mention that dcsync is for domain hashes, that the hive parameters enable offline analysis, or any prerequisites. The agent must infer usage from the name and schema alone.

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