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

With readOnlyHint/destructiveHint/openWorldHint already declared, the description adds traits the annotations don't: the episode must already be transcribed (implicit precondition), the payload is paginated by segment, and each segment carries timestamps and speakers. It stops short of covering pagination exhaustion behavior or translated-output effects on timestamps, so it's strong but not exhaustive.

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 sentences: the first states what is returned, the second routes to the alternative. Zero filler and the capability statement is front-loaded ahead of the usage caveat.

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?

With no output schema, the description usefully characterizes the return shape (timestamped, speaker-attributed segments) and the pagination model. Gaps remain around whether translation preserves timestamps and how to detect that pagination is exhausted, but for a read-only lookup tool it is close to complete.

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 seq/limit/offset/language are already fully documented, making 3 the floor. The description adds the pagination unit ('per segment'), clarifying that limit/offset operate on transcript segments rather than characters or time, which is genuine meaning beyond the schema.

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 specific verb and resource ('Get the full transcript of a transcribed episode') plus distinguishing output traits (timestamps, speakers, segment-based pagination). It explicitly separates itself from the sibling get_episode_summary, so an agent can choose between them without opening either schema.

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?

Provides an explicit routing rule: 'Prefer get_episode_summary unless exact wording or quotes are needed.' That names the alternative and the precise condition that selects this tool over it, leaving nothing to inference.

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