run_powershell

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

With no annotations, the description carries the behavioral transparency burden and does disclose meaningful traits: 'full system access', 'No restrictions', and capabilities including registry, services, network, and processes. It does not mention whether commands are destructive, what side effects might occur, or how output is returned, but the risk profile is usefully conveyed.

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 short and front-loaded with the core action, then adds risk context and capability examples. The mention of 'No restrictions - for trusted AI partners' is slightly redundant with 'full system access', but overall there is minimal fluff and every sentence contributes useful information.

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?

The description covers the safety-critical aspects of the tool and the schema documents parameters, so an agent can invoke it at a basic level. However, there is no mention of return values, error behavior, or how this tool relates to run_powershell_script, which leaves some gaps for a tool without an output schema.

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 description coverage is 100%, so the schema already documents all three parameters adequately. The description adds no additional parameter-level detail such as examples, format expectations, or timeout semantics, but since the schema covers parameters fully, the baseline of 3 is appropriate.

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 identifies the action ('Execute a PowerShell command') and resource, which is specific and unambiguous. However, it does not differentiate run_powershell from sibling tools like run_powershell_script, so while the core purpose is clear, the sibling boundary is not articulated.

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 implies this tool is for arbitrary PowerShell execution with 'full system access' but provides no explicit guidance on when to choose it over run_powershell_script or avoid it in favor of safer alternatives. There are no stated conditions, exclusions, or context for selection.

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