Ytdlp List Subtitles

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive. The description adds that subtitles are listed 'without downloading files', reinforcing the read-only behavior and clarifying what action is performed. No contradiction with annotations.

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, both essential. Front-loaded with the action and resource, followed by usage guidance. No wasted words.

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 the output schema exists, the description does not need to detail return values. It covers core purpose and usage context. However, it could briefly mention the presence of pagination parameters (limit/offset) to aid selection, but the tool is simple enough that this is not critical.

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 compensate by explaining parameter purpose or usage. It does not mention any of the 7 parameters (url, auth, limit, offset, network, flatPlaylist, responseFormat). The description focuses only on the tool's overall function, leaving parameter semantics entirely 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?

The description clearly states the action (List), resource (manual subtitles and automatic captions), and scope (for a media URL without downloading). It distinguishes from sibling tools like ytdlp_download_subtitles by emphasizing no download. The phrase 'List available manual subtitles and automatic captions' is specific and unambiguous.

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 explicitly provides a use case: 'Use when the user asks which subtitle languages or formats exist.' This gives clear context for when to invoke. However, it does not mention when NOT to use or suggest alternatives to other sibling tools like ytdlp_get_metadata, which might also provide subtitle info.

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