mimikatz_status

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The verb 'Check' suggests a read-only operation, but the description does not explicitly say so, nor does it mention whether privileges are required, whether the Mimikatz binary is actually invoked, or what failure modes exist (e.g., missing installation, incompatible system).

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 sentence with no filler. The action is front-loaded, and every word contributes meaning.

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 status check this is adequate, but with no output schema the description does not tell the agent what result to expect (e.g., boolean, version string, compatibility matrix) or how to interpret 'compatible.' The preflight role relative to sibling tools is implied, not stated.

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?

This tool takes zero parameters and the schema covers 100% of the parameter surface. There is nothing for the description to add about parameter semantics, so the no-parameter baseline of 4 applies.

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 precise action ('Check') and a clear resource ('Mimikatz installation status and system compatibility'). This clearly distinguishes it from the action-oriented sibling tools, all of which are focused on credential dumping, Kerberos operations, or other post-install activities.

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 status/compatibility framing implies this tool is a preflight check before using the other mimikatz_* tools, but the description never explicitly states when to use it or that it should precede the others. No exclusions or alternative conditions are given.

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