power_shell_read

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

No annotations are provided, so the description carries the full burden. It discloses the concurrency hazard that can corrupt the output buffer, which is important behavioral context. It doesn't mention return format or clearing behavior, but those are partially covered by the schema's 'clear' parameter.

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 sentences: the first states the purpose, the second delivers a crucial warning. Front-loaded and every word earns its place.

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 tool is simple (read output) and has no output schema. The description explains the core function and the concurrency constraint, which is essential context. It doesn't describe the return structure, but that's typical for a read tool and not required given the simplicity.

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% — both parameters ('session_id' and 'clear') are documented in the schema. The description adds no additional parameter semantics beyond the schema, so baseline 3 is appropriate.

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 states the tool's purpose clearly: 'Read output from a PowerShell shell session' — specific verb and resource. It differentiates from sibling tools like power_shell_exec and power_shell_write by focusing on reading 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?

Provides explicit concurrency guidance: 'Do NOT call this concurrently with power_shell_exec/power_shell_write on the same session_id — concurrent access to the same PowerShell process corrupts the output buffer.' This clearly instructs when not to use it and highlights a critical constraint.

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