uclass_read_transcript

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe read-only nature is established. The description adds useful context—normalized native output, published-record scope, and the expectation to cite [m:ss] timestamps—but does not address response structure or other behavioral details.

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 short sentences with the core action front-loaded; every phrase serves a purpose: what it reads, when to use it, and how to cite it. No redundancy or filler.

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?

For a read-only tool with two well-documented parameters, the description covers the operation, the triggering condition, and citation behavior. It relies on the 'evidence windows' concept being understood from the sibling search tool, and there is no output schema, but the return value is clearly a transcript.

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 courseId and recordingId are already documented, including recordingId defaulting to the latest published recording. The description adds no parameter-level detail, so the baseline 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 the action ('Read') and exact resource ('complete normalized native transcript of a published Class recording'), so an agent immediately knows what data comes back. The qualifiers 'complete' and 'evidence windows' also separate it from the search-oriented sibling uclass_search_transcript.

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 an explicit trigger: use only when evidence windows do not settle the question. It does not name the alternative search tool or describe what to do when evidence windows do settle, so it is clear but not fully explicit about the alternative path.

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