power_shell_open

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

With no annotations provided, the description carries full burden for behavioral traits. It only mentions that it opens an interactive session and returns banner, but omits critical details such as whether the session persists, how to identify the session, authentication requirements, or what happens if a session already exists.

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?

Description is a single, concise sentence that delivers the essential purpose upfront. However, it could be slightly improved by adding a brief note on expected output format or next steps without increasing length significantly.

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?

For a simple tool with one optional parameter, the description is adequate but minimal. It mentions the banner output but does not clarify whether a session identifier is returned for subsequent interactions, which is important given the sibling tools (power_shell_read/write/exec/close).

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% for the single parameter 'workingDir', and its description already explains the default behavior. The tool description adds no additional meaning beyond what the schema provides, meeting the baseline expectation for parameter semantics.

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?

Description clearly states it opens an interactive PowerShell shell session on the local Windows machine and returns the initial banner output. This verb+resource specificity distinguishes it from sibling tools like power_shell_exec or power_shell_close.

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?

Description implies usage as a session opener before other PowerShell commands, but does not explicitly state when to use this tool versus alternatives like power_shell_open vs power_shell_exec. No exclusion or when-not guidance is provided.

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