run_powershell_script

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

With no annotations, the description carries the burden of safety disclosure, and it does warn about 'Full system access' and 'MCP-safe subprocess handling.' However, it does not explain that scripts can make arbitrary system changes, how errors are surfaced, or whether stdout/exit codes are returned.

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 short sentences with the core purpose front-loaded and no filler. The risk-related warning is separated clearly and does not distract from the main action.

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?

All parameters are documented in the schema and the tool's risk level is stated, which covers the basic invocation requirements. However, the description omits return/error behavior and any relationship to 'run_powershell,' which leaves meaningful gaps for a high-risk execution tool with no 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 four parameters. The description adds only 'with arguments,' which provides no meaningful semantic value beyond what the input schema already states.

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 uses a specific verb ('Execute') and a specific resource ('PowerShell script file (.ps1)') and explicitly mentions arguments, so an agent immediately understands the tool's function. The file-based scope also helps distinguish it from the sibling 'run_powershell' tool, which likely handles inline PowerShell commands.

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 choose this tool over 'run_powershell' or the other script execution siblings, and it mentions no exclusions or prerequisites. 'Full system access' hints at caution, but there is no explicit decision context.

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