powershell_exec

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

No annotations are provided, so the description must convey behavioral context. It merely states 'Execute a command' and 'Supports all PowerShell cmdlets and scripts,' without disclosing side effects, permissions, output format, or error handling. For a command execution tool, this is a significant omission.

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?

Two sentences, direct and front-loaded. No unnecessary detail; every word earns its place. However, it may be too concise to cover the tool's complexity, but as a concise opening statement it works.

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 its high complexity (arbitrary PowerShell execution) and lack of output schema/annotations, the description is incomplete. It doesn't describe return values, behavior on errors, or safety considerations. It leaves out essential context.

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 already provides descriptions for all three parameters (command, env, working_dir), covering 100%. The description adds no additional parameter-level meaning beyond the schema.

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: executing commands in Windows PowerShell. It distinguishes itself from the sibling cmd_exec by naming 'Windows PowerShell' specifically, and 'Supports all PowerShell cmdlets and scripts' reinforces its scope.

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 use for PowerShell-specific tasks but provides no explicit guidance on when to choose it over alternatives like cmd_exec, nor any exclusions or prerequisites.

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