mimikatz_misc_cmd

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 does clearly state the core behavior: spawning a command prompt with the current, potentially elevated context. However, it does not disclose whether the prompt is interactive or blocking, what side effects occur, or what the tool returns, so the transparency is only minimally adequate.

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 tight sentence with no filler. Every word contributes meaning, and the main action ('Spawn a command prompt') is front-loaded before the contextual detail.

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-parameter tool this is close to adequate, but the absence of annotations and an output schema means the description should clarify what happens after the prompt spawns or offer a usage cue, such as running it after privilege elevation. The lack of any such context, amid 20 similar tools, leaves the agent guessing about the result of invocation.

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 the baseline is 4. The description correctly avoids inventing parameter details that do not exist and introduces no ambiguity.

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 direct verb ('Spawn') and identifies a concrete resource ('a command prompt') with an explicit scope ('current (potentially elevated) context'). This makes it distinguishable from the credential-dumping and Kerberos-focused sibling tools, though it does not explicitly name an alternative the way the strongest definitions do.

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 siblings like mimikatz_token_elevate, mimikatz_privilege_debug, or the credential-recovery tools. The agent is left to infer that this is the 'run an arbitrary shell' tool among 20 similar Mimikatz commands.

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