mimikatz_dpapi_masterkey

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Decrypt DPAPI master keys' implies an operation but does not explain side effects, required privileges, whether SYSTEM hive access is mandatory, what happens when keys are missing, or what the output looks like.

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 wasted words. It efficiently states the core action and resource, making it easy 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?

Given there are no annotations, no output schema, and the tool operates on security-sensitive DPAPI data, the description is too sparse. It lacks necessary context about when an agent should choose this tool, what inputs are expected in practice, and what result or side effects to anticipate.

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 baseline is 3. The description adds no extra meaning beyond what the schema already states for 'guid' and 'system'; it does not clarify how the parameters interact or whether both are 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 states a clear verb and resource: 'Decrypt DPAPI master keys.' This is specific enough to identify the tool's function within the mimikatz family, but it does not explicitly contrast it with siblings such as mimikatz_lsadump_secrets or mimikatz_crypto_certificates, so it falls short of full differentiation.

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 like mimikatz_custom or other DPAPI-related operations. No context is given about online versus offline use cases, prerequisites, or typical workflow placement.

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