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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restating. The description adds real context beyond them: the transcript is raw, it is scoped to a single participant, and questionRef narrows a long interview to a slice — behavior an agent would not learn from the annotations alone.

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, both load-bearing: the first defines the resource and payload, the second covers the optional narrowing parameter. No filler and the resource definition is front-loaded.

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 an output schema present, the description needn't explain return values, and annotations carry the safety profile. Purpose, scoping and the optional filter are all covered; only the relationship to sibling transcript tools and behavior for an unknown participant/testId are left unstated.

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 coverage is 100%, so baseline is 3; the description earns above that by explaining the semantic effect of questionRef (reading only that part of a long interview) rather than just restating that it is a guide ref. It still says nothing about questionRef interacting with pagination or ordering of the returned turns.

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 ("Read one participant's raw transcript from an AI-moderated study") and even enumerates the content returned (moderator/participant turns, timestamps, quote refs). It does not name the obvious alternatives (get_transcript, search_interview_transcripts), so an agent must infer which of several transcript-related siblings to pick.

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 second sentence gives a concrete usage rule for the optional parameter ("Pass questionRef to read just that part of a long interview"), and the schema props point back to get_interview_study. However, there is no when-to-use / when-not-to-use guidance relative to search_interview_transcripts or get_transcript, leaving the sibling choice implicit.

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