mimikatz_lsadump_secrets

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

No annotations are provided, so the description must disclose behavioral traits. It only states the operation, not requirements like elevated privileges, potential side effects, or the sensitivity of the output. The word 'Dump' implies reading secrets but gives no further safety or context information.

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. The parenthetical example adds useful clarification without bloating the text.

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?

With no annotations, no output schema, and a security-sensitive operation, the description is too thin. An agent would benefit from knowing expected output, required privileges, and how this relates to the many sibling mimikatz tools. The invocation is simple due to zero parameters, but the behavioral context is missing.

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?

There are zero parameters, so the description does not need to document parameter details. The baseline for a no-parameter tool is 4, and the description adequately focuses on the tool's action rather than any inputs.

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 uses a specific verb and resource: 'Dump LSA secrets' with an example of the contents ('service account credentials, etc.'). It identifies the target clearly, though it does not explicitly contrast this with sibling lsadump tools like mimikatz_lsadump_sam or dcsync.

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 guidance on when to use this tool versus alternatives such as mimikatz_lsadump_sam or mimikatz_lsadump_dcsync. The description implies it is for LSA secrets but provides no context, prerequisites, or exclusions.

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