Get playlist transcripts

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description adds value by specifying that subtitles are 'cleaned (plain text)', which is a behavioral trait not inferable from annotations. No contradictions.

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, each serving a purpose: first describes the core function, second explains key parameter usage. No extraneous words. Highly efficient.

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?

Given 6 parameters, 100% schema coverage, output schema exists, and annotations present, the description covers the core functionality and critical parameters. Minor gap: no mention of return format or error conditions, but output schema likely covers that.

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 goes beyond by providing concrete examples for playlistItems and maxItems ('1:5', '1,3,7'), adding meaning to those parameters.

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 clearly states 'Fetch cleaned subtitles (plain text) for multiple videos from a playlist.' It uses a specific verb ('Fetch'), identifies the resource ('cleaned subtitles for multiple videos from a playlist'), and distinguishes from sibling get_transcript (single video) by specifying 'multiple'.

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 usage hints for playlistItems and maxItems (e.g., 'Use playlistItems (e.g. "1:5") to select specific items, maxItems to limit count.'), but does not explicitly contrast with siblings like get_transcript or get_raw_subtitles. However, the context of 'multiple videos from a playlist' implies the distinction.

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