process_read_output

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

With no annotations provided, the description fully carries the burden and does so well: it explicitly discloses that lines are returned and removed from the buffer, that category filtering drains only that category, and that unconsumed lines remain buffered. This is exactly the side-effect visibility an agent needs.

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?

Two dense, efficient sentences with no filler. The core action and side effect are front-loaded, and the filtering edge case is explained clearly in the second sentence.

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 small two-parameter tool with no output schema, the description supplies the action, buffer semantics, filtering behavior, and retention rule. An agent can invoke it correctly and predict follow-up behavior without needing additional inference.

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%, so the baseline is 3. The description adds meaningful behavioral nuance beyond the schema: filtering by category leaves other categories buffered, and matches beyond maxLines are preserved for later calls. This directly affects agent decisions about follow-up invocations.

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 ('Drain') with a clear resource ('buffered output (stdout/stderr) from the debuggee') and a precise temporal scope ('since the previous call'). This clearly differentiates it from sibling debugger tools such as stacktrace_get or trace_get.

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 implies usage: after debugger execution, drain collected output, and 'stay buffered for a later call' explains repeated draining. However, it never names alternatives or states when not to use this tool, leaving some routing to inference.

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