Read buffered serial output from a connected hardware session without transmitting data; use it to drain the current buffer, and prefer history for lossless capture.
Read buffered serial output without sending anything (session drain; prefer history for lossless capture).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower, and the description still adds real behavioral context: this is a 'session drain' whose contents are consumed, versus history which is lossless. That drain/loss nuance is not expressed anywhere in the structured fields and is the most decision-relevant thing an agent needs to know.
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 sentence with the core action front-loaded and the alternative-route caveat tucked into a parenthetical. Every clause earns its place; nothing is padded or repeated from the schema.
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?
For a zero-parameter, read-only tool with no output schema, the definition supplies the action, the consumption semantics, and the better alternative for lossless capture. It leaves the return format and whether the drain actually clears the buffer implicit, which is a minor gap given the tool's 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?
The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The absence of arguments is consistent with the description's claim that nothing is sent.
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?
States a specific verb and resource ('Read buffered serial output') plus a scoping constraint ('without sending anything'), which is far more than a restatement of the name. It differentiates itself from serial_output_history by naming that sibling as the lossless alternative, though it does not distinguish itself from the other serial_* siblings (monitor, wait_for, status).
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 parenthetical 'prefer history for lossless capture' gives an explicit alternative and the condition that selects it, which is exactly the routing guidance an agent needs between two similar read tools. It stops short of a full when/when-not statement (e.g. no guidance relative to serial_monitor or serial_wait_for), so it is clear context rather than complete routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.