Read one conversation transcript

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

With no annotations provided, the description carries the full behavioral burden. It explicitly states the operation is read-only and describes the output shape: full turn list, ordered, with topic and tool attribution where recorded. The caveat 'where the transcript records them' also sets expectations about incomplete data, though it does not cover error behavior or authentication edge cases.

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 sentence that front-loads the core purpose ('full turn list of one session') and then adds the necessary detail about content and ordering. Every phrase earns its place with no redundancy.

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 6-parameter tool with only one required parameter and no output schema, the description adequately explains what the tool returns. It also notes the read-only nature and the conditional attribution of topic/tool. It could be slightly stronger by explicitly routing the user to cs_list_transcripts for obtaining transcriptId, but the schema already mentions that source.

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%, so the parameters are already fully documented by the schema. The description adds no parameter-specific meaning beyond the schema, but it does not need to; baseline 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 description states a precise verb-resource pair: it reads one conversation transcript and returns the full turn list. It further specifies what is included (who said what, in order, with topic/tool attribution), which clearly distinguishes it from sibling tools like cs_summarize_transcripts or cs_list_transcripts.

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 this tool is for retrieving the raw turn-level transcript of a single session, and the title reinforces that intent. However, it does not explicitly name alternatives or state when not to use it, such as pointing to cs_summarize_transcripts for summaries or cs_list_transcripts for finding transcript IDs.

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