mimikatz_privilege_debug

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

With no annotations, the description carries the full behavioral burden. It states the core action—enabling SeDebugPrivilege—but does not disclose whether administrator rights are required, whether the change is scoped to the current process, whether it persists, or any security 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 one short sentence that front-loads the action, names the specific privilege, and states its purpose. Every word contributes meaning; there is no padding or repetition of the tool name.

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 zero-argument utility, the description is adequate: it names the effect and the intended use. However, it omits useful operational context such as required elevation, the fact that SeDebugPrivilege is typically disabled by default, and its relationship to other mimikatz commands that depend on it.

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, so the description is not responsible for explaining parameter behavior. The baseline for zero-parameter tools is 4, and no parameter-semantics gap exists.

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: 'Enable SeDebugPrivilege,' and 'for process manipulation' explains why this capability matters. This clearly distinguishes the tool from the credential, Kerberos, and LSASS-dump siblings.

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?

The phrase 'for process manipulation' implies this is a prerequisite or setup step for process-related tasks, but it does not explicitly state when to run this tool versus alternatives like token_elevate or process_list, nor does it note that many other mimikatz commands require SeDebugPrivilege first.

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