terminal_read

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

No annotations are provided, and the description does not disclose key behaviors such as whether reading clears the buffer, whether it blocks, or what happens when maxChars is exceeded. The term 'buffered' is ambiguous—does it return all buffered output since last read, or only new? The description lacks sufficient behavioral context.

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, clear sentence that communicates the core function efficiently. It is appropriately front-loaded with the verb and object. However, it could include brief parameter guidance without becoming verbose.

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 simplicity of the tool, the description is minimally sufficient but lacks key contextual details such as the need for an active session, the non-realtime nature of buffered output, and the effect of the maxChars parameter. It does not explain the interaction with other terminal tools (e.g., terminal_start must be called first).

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?

The description does not mention the parameters sessionId or maxChars at all. The schema has no descriptions for these fields, yet the description adds no information about their purpose or constraints. For example, it does not specify that sessionId must identify an active terminal session or that maxChars limits the number of characters returned.

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 'Read', the resource 'buffered stdout/stderr', and the context 'from a persistent terminal session'. It distinguishes from sibling tools like terminal_write (write) and terminal_start (start session).

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 does not provide any guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., need a started session) or scenarios where other tools like run_command or terminal_write would be more appropriate. It simply states the function.

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