output

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

With no annotations, the description carries the full burden, but it discloses almost nothing: whether the call blocks until a turn completes, what happens if no turn has occurred yet, or whether it is a pure read. Only the notion of 'most recent turn' hints at recency semantics.

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 short sentence with no filler, front-loading the returned artifact. It is terse to the point of being a fragment, but nothing is wasted.

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 means return values need not be explained, but with 16 siblings and a generic name like 'output', the description should clarify retrieval semantics, blocking behavior, and error conditions. Too much is left to inference for an agent choosing among close alternatives.

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 100% and the single required 'session' parameter is documented in the schema as an id returned by open, so the schema does the heavy lifting. The description adds nothing about which session or how the parameter scopes the returned turn.

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 fragment 'Final reply of the most recent turn' implies a retrieval of the last assistant reply for a session, which is a discernible purpose. However it omits the verb entirely and gives no way to distinguish it from siblings like progress, status, item, or snapshot, which could all plausibly return per-session content.

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 statement of when to call this versus the many sibling read/monitoring tools. An agent must infer that this is the way to read the last reply, with no conditions or exclusions offered.

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