Read one conversation transcript

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

With no annotations, the description carries the full burden; it declares 'Read-only' and discloses that attribution is only present 'where the transcript records them,' which usefully signals optional fields. However, it says nothing about auth requirements (the clientId/tenantId/botId params imply MSAL auth), pagination, or size limits on a potentially long transcript.

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?

Two tight sentences with the payload content front-loaded and the read-only qualifier trailing; nothing is redundant or padded.

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?

There is no output schema, so the description must describe returns, and it does — turn ordering, speakers, and per-turn topic/tool attribution. The main gap is pagination/truncation behavior for long transcripts, which matters for a tool returning a full turn list.

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 all six parameters are documented in the schema, including defaults and the transcriptId source. The description adds return-shape context but no parameter meaning beyond that, so the baseline of 3 applies.

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 concrete verb and resource ('the full turn list of one session') and even previews the payload shape (speaker, order, topic/tool attribution). It implicitly separates itself from cs_list_transcripts and cs_summarize_transcripts by emphasizing 'full turn list,' but it never names an alternative explicitly.

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 when-to-use or when-not-to-use guidance. The routing hint ('from cs_list_transcripts') lives in the transcriptId schema description, not the description itself, so an agent gets no explicit instruction about when to reach for this versus cs_summarize_transcripts.

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