get_lesson_transcript

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

With no annotations provided, the description carries the full transparency burden. It discloses the error behavior for non-video lessons, explains the format parameter's two modes, and states the exact return shape. It does not explicitly mention whether the operation is read-only, but the verb 'fetch' strongly implies it, and no hidden side effects are suggested.

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?

The description is compact and well-structured: a one-sentence purpose, a concise args list with practical guidance, and a return/error note. Every sentence adds useful information and nothing is redundant.

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 tool with no annotations and no output schema, the description covers all essential aspects: what it does, how to populate each parameter, what the return object contains, and when it will fail. No critical information needed to call it correctly is missing.

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 0%, so the description must fully compensate. It explains the provenance of course_slug and lesson_slug, gives an example format for lesson_slug, and details the two enum values for format with behavioral descriptions. This goes far beyond the bare string/enum 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?

The description opens with 'Fetch the full transcript for one video lesson,' which is a specific verb and resource. It clearly distinguishes itself from sibling tools like get_lesson_frame and get_lesson_slides by focusing solely on transcripts, and further clarifies that only video lessons are supported.

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 description provides clear context on when to use this tool: for video lesson transcripts. It explicitly warns that 'other lesson types raise an error,' giving a when-not condition. It also specifies the source of each slug (from list_enrolled_courses and list_lessons), though it does not explicitly name alternative tools for non-video content.

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