winrm_exec

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

With no annotations, the description must carry the transparency burden. It discloses one important behavior ('Output captured in-process (no console window)') and notes the WinRM requirement, but it does not elaborate on authentication needs, potential side effects, or exit code handling. This is a moderate level of disclosure.

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 two sentences that are tightly packed with essential info: action, method, target, key differentiator, and output behavior. Every clause earns its place, with no fluff or redundancy.

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 (7 parameters, no output schema), the description covers the core essentials: what it does, how it connects, and a key behavioral detail. It lacks some operational nuance like return value format or explicit rest of the lifecycle, but it is largely complete for an agent to invoke 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?

Schema coverage is 100% with well-described parameters, so the baseline is 3. The description does not add parameter-specific meaning beyond what the schema already provides, such as elaborating on the command field or authentication options. It remains at baseline.

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's function: 'Run a command on a remote Windows host via PowerShell Remoting' and distinguishes it from SSH-based alternatives by explicitly noting 'no SSH server or agent needed.' This makes the purpose immediately apparent and differentiates it from siblings like ssh_exec.

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?

It provides clear context on when to use the tool: when targeting Windows hosts with WinRM enabled. The explicit mention that SSH is not needed serves as an implicit alternative, but it does not explicitly state 'use this instead of ssh_exec' or address run_powershell, so it falls short of full exclusionary guidance.

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