serial_read

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

With no annotations, the description carries the full burden, but it only states that it reads output without disclosing buffer behavior, blocking semantics, or side effects. The 'clear' parameter in the schema hints at buffer clearing, but the description itself doesn't mention it or any other behavioral traits.

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 concise sentence that front-loads the action and resource. It is appropriately sized for a simple read operation, with no wasted words.

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 description is minimal and does not explain return value format, whether it blocks, or how it interacts with the session lifecycle. Given there are many sibling read tools and no output schema, the description is insufficient for an agent to fully understand when and how to invoke this 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 100% with both parameters described, so the baseline is 3. The description adds no additional parameter information beyond the schema, but the schema descriptions for 'session_id' and 'clear' are already clear.

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 the verb 'read' with the resource 'output from a serial shell session', clearly identifying the tool's function. It distinguishes from sibling write/exec tools by specifying the read action, though it lacks scope details like whether it clears the buffer or returns all pending 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 provides no guidance on when to use this tool instead of alternatives such as serial_exec or ssh_shell_read. It does not state prerequisites like having an open session, nor does it mention situations where it would be preferred.

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