power_shell_exec

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

With no annotations provided, the description carries the behavioral disclosure burden. It discloses the combined operation flow (write + delay + read), indicates the one-way session nature, and highlights the critical concurrency/interleaving hazard. It doesn't cover timeout, error, or return-value behavior, but the core behavioral traits are transparent.

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 sentences, front-loaded with the primary purpose, and includes a crucial operational warning. No filler or redundant repetition of schema 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 core behavior and concurrency rule, which is essential context. However, with no output schema and no annotations, it omits return-value details (e.g., stdout, stderr, exit code), failure behavior, and timeout semantics, leaving some uncertainty for an agent invoking this tool.

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 parameters. The description adds minimal parameter-level insight beyond the combined operation concept; it doesn't elaborate on `clear`, `delay`, or `command` semantics beyond the schema definitions.

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 action: 'Send a command to a PowerShell shell session and wait for the output.' It further distinguishes itself by explaining that it combines write + delay + read in one call, setting it apart from sibling tools like power_shell_write and power_shell_read.

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 explicit usage guidance by warning against concurrent commands and instructing the agent to wait for the previous command to finish. It implies this tool is the synchronous alternative to manually chaining write/read calls, though it doesn't explicitly enumerate alternatives.

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