winrm_execute_powershell

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 states that it returns stdout, stderr, and exit code, but does not describe system impacts, authentication/connection requirements, side effects, or error handling. This is minimal disclosure for a remote execution tool.

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, concise sentence that immediately conveys the core action and expected outputs. It is front-loaded and free of filler, though it omits necessary details.

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?

With 8 parameters, no schema descriptions, no annotations, and a sibling tool that likely covers similar functionality, the description is far from complete. It only addresses the basic execution and return values, leaving parameter meanings, usage context, and alternative selection unexplained.

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 descriptions for its 8 parameters, and the description mentions only 'PowerShell command' without elaborating any of the parameters (command, cwd, env, timeout, connection, saved_host, output_limit, inventory_scope). The description fails to compensate for the 0% schema coverage.

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 a specific verb ('Execute'), a resource ('PowerShell command over WinRM'), and the expected outputs ('stdout, stderr, and exit code'). This is specific enough to distinguish from the likely cmd-based sibling winrm_execute_cmd, though it does not explicitly name alternatives.

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 the sibling tools, especially winrm_execute_cmd or winrm_test. It does not mention preferred contexts, prerequisites, or exclusions.

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