remote_session_output

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

No annotations are provided, so the description carries the burden. 'Read' implies a non-mutating operation and 'recent' clarifies scope, but it does not disclose whether reading consumes the buffer, whether it returns all output or only new output, or any permissions needed.

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?

A single, front-loaded sentence with no fluff. Every word adds meaning: 'recent', 'raw', 'session buffer'. Highly concise and scannable.

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 and the description covers the core action, but without annotations or an output schema it leaves open questions about return format, buffer consumption, and session selection. Minimum viable for a basic read 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 coverage is 50%: 'lines' is described but 'sessionId' is not. The description adds minimal parameter meaning, only implying that output is tied to a session buffer and recentness. It does not clarify that sessionId is optional or what it defaults to, leaving a semantic gap.

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 uses a specific verb ('Read') and resource ('recent raw output from session buffer'), clearly distinguishing it from siblings like remote_session_history, remote_session_errors, and remote_session_status. The scope ('recent', 'raw') adds precision.

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?

No guidance on when to use this tool versus alternatives such as remote_session_history or remote_session_errors. It does not state exclusions or mention that sessionId is optional/required, leaving usage context to inference.

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