power_shell_read

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

No annotations are provided, so the description carries full burden. It does not disclose critical behavioral traits such as the default buffer-clearing behavior (clear=1) or whether reading is blocking. The agent is left unaware that reading consumes the buffer unless clear=0.

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, well-structured sentence with no wasted words. It is front-loaded and easy to parse. However, it could be slightly more detailed without sacrificing conciseness.

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 the tool has two parameters and no output schema, the description is incomplete. It omits essential context such as the need for an open session, the default buffer-clearing behavior, and the relationship with power_shell_open. The agent may not fully understand usage prerequisites.

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 the baseline is 3. The description itself adds no extra meaning beyond what the schema already provides for both 'session_id' and 'clear'. It does not elaborate on usage or format.

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 'Read output from a PowerShell shell session,' which is a specific verb+resource. It distinguishes from sibling tools like power_shell_open, power_shell_exec, and power_shell_close as the dedicated read operation for shell output.

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 after opening a session and executing commands, but it does not explicitly state when to use versus alternatives (e.g., power_shell_exec already returns output, but this tool reads buffered output). No when-not or alternative guidance is provided.

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