nxc_wmi

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

With no annotations, the description must fully describe behavioral traits. It only states the basic action (execute commands) without disclosing potential side effects, authentication methods, required permissions, or any destructive nature. The description is too minimal to provide transparency.

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, concise and front-loaded. While it lacks depth, it is not verbose and wastes no words.

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 command execution tool with 7 parameters, no annotations, and no output schema, the description is insufficient. It fails to explain return values, error handling, security considerations, or any common usage patterns. The description feels incomplete.

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?

Input schema has 100% description coverage, so each parameter is already documented. The tool description adds no additional meaning beyond the schema, earning a baseline score of 3.

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 clearly states the tool executes NetExec WMI protocol commands for Windows management and command execution. It uses a specific verb and resource and distinguishes itself from sibling tools like nxc_smb or nxc_ldap by naming WMI.

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 description provides no guidance on when to use this tool versus alternatives (e.g., WinRM, SMB). There is no mention of prerequisites or scenarios where WMI is preferred.

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