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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuine behavioral context beyond them: pagination semantics, that limits are measured in characters, legacy-test support, and the default behavior when block/run is omitted. The phrase "documented defaults" is slightly circular rather than stating the actual defaults.

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?

Five short, front-loaded sentences that lead with the core action before routing and pagination details. Efficient overall, though "omission uses the documented defaults" is vaguely worded filler rather than a concrete default value.

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?

An output schema exists, so return values need not be described. Combined with annotations and the routing/pagination guidance, the definition is nearly complete; the remaining gaps are the unexplained testId and the circular reference to "documented defaults" for block/run omission.

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 only 17%, so the description must compensate, and it does for most parameters: ref's source (list_transcripts), limit's unit (characters), offset as pagination, and blockId/runId sourced from list_test_blocks. Only testId lacks added meaning, and the limit bounds/max are left to 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 ("Read a session transcript") and immediately scopes it to "by exact ref from list_transcripts," distinguishing it from the sibling list_transcripts and from get_test_question_responses. An agent knows exactly what this returns without opening the 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?

Explicitly routes the agent: post-test answers go to get_test_question_responses, refs come from list_transcripts, and block/run IDs come from list_test_blocks. It also states the pagination path (offset/limit) and that legacy tests are supported, covering both when-to-use and when-not-to-use.

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