power_shell_exec

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

With no annotations, the description carries the burden of disclosing behavior. It mentions waiting for output and the combined write/delay/read sequence, but it does not disclose buffer clearing behavior, default delay timing, session requirements, error semantics, or whether output is fully captured. This is adequate but not rich.

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 a single, front-loaded sentence that conveys purpose and distinguishing behavior without redundancy. It earns its place by adding the write/delay/read combination detail.

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 command execution tool with no output schema and no annotations, the description is reasonably complete but leaves gaps: it doesn't state that the session must already be open (though session_id is required) or describe what the returned output looks like. It is acceptable but not comprehensive.

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%, so baseline is 3. The description adds value by clarifying the operational sequence (write + delay + read), which helps the agent understand how the command, delay, and clear parameters interact. This goes beyond the schema's field-level 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 verb ('Send a command'), the resource ('PowerShell shell session'), and the expected behavior ('wait for the output'). It also explicitly notes that it combines write, delay, and read, distinguishing it 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 implies usage by stating it combines write + delay + read in one call, indicating it is for executing a command and getting output without separate steps. However, it does not explicitly name alternative tools or state when not to use it, so it falls short of a perfect score.

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