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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral detail: matching is case-insensitive and accepts any term, and results are capped at 40 participant turns, each carrying quote refs and the preceding moderator prompt — the cap is operationally important and appears nowhere else.

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 tight sentence that front-loads the action and scope, then the matching and result characteristics. No filler, nothing an agent must read twice.

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, return shape need not be spelled out, and annotations cover the safety profile; the description still adds the 40-turn cap. Minor gaps remain around multi-term semantics (are terms OR'd or AND'd?) and whether the result cap can be paged past.

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 terms, testId and questionRef are all documented in the schema (including the synonym/language hint and the "Q2" ref format). The description adds no syntax or constraint detail beyond naming the domain, so the baseline 3 is correct.

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 ("Search what participants said") plus scope ("across all interviews of an AI-moderated study"), which distinguishes it from single-transcript siblings like get_interview_transcript. It does not, however, differentiate itself from the sibling search_quotes, which an agent could easily confuse it with.

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?

Usage is implied by "across all interviews" (broad search rather than one transcript at a time), but there is no explicit when-to-use / when-not-to-use statement and no mention of when to prefer search_quotes or get_interview_transcript instead. The optional questionRef is also not framed with a condition for using it.

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