Read a delegated OpenCode session's transcript

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

No annotations are provided, so the description bears the full burden. It clearly states that the tool is non-blocking ('without waiting for it to finish') and returns the current conversation. It does not mention error behavior or side effects, but for a simple read operation, this is adequate.

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 description is a single, concise sentence that includes the core functionality and key constraint ('without waiting for it to finish'). No superfluous words.

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?

Given the low complexity (3 parameters, all described in schema) and no output schema, the description covers the essential behavior. However, it misses hinting at the return format, which would improve completeness. Minor gap.

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 tool description adds no extra meaning beyond what the schema already provides for the three parameters (sessionId, tail, includeToolCalls). Baseline of 3 is appropriate.

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 title and description clearly state that this tool fetches the transcript of a delegated OpenCode session without waiting for it to finish. The verb 'Fetches' and resource 'conversation so far' are specific, and it distinguishes from siblings like ode_delegate and ode_await.

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 indicates it is for sessions started by ode_delegate and that it returns the conversation without blocking, implying it is useful for reading ongoing sessions. However, it does not explicitly state when to use alternatives like ode_await or ode_cancel, though sibling names provide implicit context.

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