power_shell_exec

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

No annotations provided, so the description bears full burden. It discloses the basic behavior (send, wait, read) and the combined nature, but lacks details on error handling, timeout effects, side effects on session state, or safety considerations for arbitrary PowerShell commands.

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 concise, front-loaded sentences with no wasted words. The first sentence clearly states the action, and the second provides additional context efficiently.

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?

With no output schema, the description does not explain the return value format. It covers the combined operation concept and the four parameters, but missing details on error outputs, timeout behavior, and potential side effects reduce completeness for a command execution 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%, providing baseline. The description adds the context that the tool combines write+delay+read, which relates to the parameters, but does not add significant meaning beyond the schema's own parameter descriptions.

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 sends a command to a PowerShell session and waits for output, distinguishing it from sibling tools like power_shell_write, power_shell_read, and power_shell_open/close by emphasizing it combines write, delay, and read into one call.

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 usage context: use this for a combined write-delay-read operation, implying separate tools for stepwise actions. However, it does not explicitly state when not to use it or mention alternatives beyond the combination.

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