youtube_list_playlist_items

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

With no annotations, the description carries the full burden of disclosing behavior. It lacks details on pagination, rate limits, authentication requirements, or output format. A simple 'List videos' is insufficient for full transparency.

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?

While the description is short (5 words), it is under-specified. True conciseness provides sufficient information in few words; here, important context is missing, making it inadequate rather than concise.

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 presence of pagination (page_token) and limit (max_results) parameters, the description should explain these but does not. Without output schema, more behavioral detail is needed. The description covers only the minimal function.

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?

The input schema has 0% parameter description coverage, and the description adds no information about the four parameters (api_key, playlist_id, max_results, page_token). An agent receives no guidance on parameter usage or expected values.

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 explicitly states 'List videos in a YouTube playlist,' clearly indicating the action (list) and resource (videos in a playlist). This distinguishes it from sibling tools like youtube_list_playlists (lists playlists) and youtube_get_video (retrieves a single video).

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?

No guidance is provided on when to use this tool versus alternatives, nor are prerequisites or conditions mentioned. The description only states the basic function without any contextual guidance.

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