read

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only says 'accumulated output' without explaining drain semantics, blocking behavior, timeouts, or ANSI handling. These behaviors are implied by the parameters but not described in prose.

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 sentence that immediately states the function. It is appropriately brief and front-loaded with the key verb and object, with 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?

This is a read operation with 5 parameters, no output schema, and no annotations. The description does not explain return format, buffer behavior, blocking/timeout behavior, or how it relates to open_session/close_session. For such a nuanced tool, the description is too minimal to be fully actionable.

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?

The schema description coverage is 60%, with drain and strip_ansi having descriptions, but max_bytes, session_id, and timeout_ms lack descriptions. The tool description adds no parameter semantics beyond what the schema provides, leaving three parameters unexplained. It does not compensate for the coverage gaps.

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 'Read' and a clear resource ('accumulated output from a session'), which distinguishes it from sibling tools that send or run. However, 'accumulated output' is somewhat vague and could benefit from specifying whether it's terminal output or something else.

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 gives no guidance on when to use this tool versus alternatives like send or run. It does not mention prerequisites, typical scenarios, or when not to use it. The single sentence offers no context for selection.

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