next_chunk

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

No annotations are provided, so the description carries the full behavioral burden. It reveals the output comes from a buffer, but says nothing about whether returned lines are consumed/removed from the buffer, whether the call blocks waiting for new output, or any rate/ordering behavior. For a chunked-stream-read tool this is a notable gap.

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 purpose sentence is front-loaded and the argument list is compact and waste-free. The Args block is slightly redundant with the schema but efficient.

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?

An output schema exists, so return-value structure needn't be described. However, the description omits the buffering prerequisite, consumption semantics, and empty-buffer behavior, leaving real gaps for a tool that coordinates with start_buffering/stop_buffering.

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 0% (bare types only), so the description must compensate, and it largely does: it explains nlines as a maximum line count with default 50 and pattern as an optional regex filter that limits results to matching lines. It doesn't clarify interaction between pattern filtering and the nlines cap, but the semantics are substantially covered.

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 a specific verb and resource ('Return the next batch of buffered serial output lines'), which is clear and unambiguous. It doesn't explicitly differentiate itself from the siblings start_buffering/stop_buffering, though the distinction is inferable from the name and wording.

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?

There is no guidance on when to call this versus alternatives. Critically, it never states the obvious prerequisite that buffering must be active (via start_buffering) before chunks can be returned, nor what happens when the buffer is empty.

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