get_output

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

With no annotations, the description carries the full burden and does well: it discloses per-launch buffering, the 1000-entry cap, telemetry/DWARF-noise filtering, and lifecycle limits. It omits permission or concurrency considerations, but the behavioral picture is otherwise rich.

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?

Four sentences, each earning its place: purpose first, then buffering behavior, then lifecycle window, then the pagination how-to. No filler or repetition.

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?

No output schema exists, and the description compensates by naming the cursor field (nextSince) used for continuation and implying the entry-list return. Combined with the limit/hasMore schema text, an agent has enough to call and page correctly.

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 67%, and the description meaningfully compensates by explaining the cursor contract ('pass since=nextSince from the previous response to fetch only new output'), which ties into the pagination semantics. limit and sessionId remain schema-documented only.

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 (Get) and resource (debuggee output: stdout/stderr/console) scoped to a session. Clearly distinguished from siblings like get_variables or get_stack_trace, which retrieve different data.

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?

Explains the temporal window ('works while running and after it finishes, until the session is closed') and how to page with since=nextSince, but gives no explicit when-not guidance or named alternative. Usage is implied by the output-retrieval framing rather than stated as a choice among siblings.

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