ad_wmiexec

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 transparency. The description 'WMIExec.' discloses nothing about side effects, required privileges, network interactions, or the type of execution performed. It gives the agent no understanding of what happens when the tool is invoked.

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 extremely short, but this is under-specification rather than genuine conciseness. It does not earn its place by conveying useful information; it merely restates the tool name. A single word or fragment cannot adequately describe a tool with four parameters and complex behavior.

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 the tool's complexity (remote command execution via WMI) and the lack of annotations or output schema, the description is completely inadequate. It provides no operational context, parameter details, or return expectations. The agent has no basis for selecting or invoking this tool correctly.

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 schema has four required parameters (domain, username, password, target) with no descriptions, and the schema description coverage is 0%. The description does not add any meaning to these parameters, failing to compensate for the lack of schema documentation. The agent receives no hints about expected formats, semantics, or relationships between parameters.

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 'WMIExec.' is a bare restatement of the tool name without a verb, resource, or scope. It does not clarify what the tool does, such as executing a command on a remote Windows host via WMI. It is essentially a tautology, providing no purpose clarity beyond the name.

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 ad_psexec, ad_evil_winrm, or ad_secretsdump. The description gives no context about the intended use case, prerequisites, or scenarios where this tool is preferred.

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