youtube_list_playlists

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

With no annotations, the description must carry the full burden. It discloses a max_results ceiling (max 50) and explains the 'mine' parameter's behavior, but it does not mention authentication requirements, what happens if both channel_id and mine are provided, or what the response contains beyond 'playlists'. This leaves several behavioral gaps.

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 efficiently concise: one sentence stating the purpose followed by a clean parameter list. Every element earns its place, with no redundant or verbose content.

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 tool's simplicity (3 params, no output schema, no annotations), the description covers the core functionality and parameter semantics but omits important contextual details like authentication, return value format, and precedence when both channel_id and mine are set. It is minimally viable but not thorough.

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 schema has zero description coverage, so the description compensates by explaining all three parameters: channel_id for source channel, mine for authenticated user's playlists, and max_results for count with an explicit maximum. This adds meaningful context beyond the bare schema types and defaults, though it omits edge-case behavior.

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 'List playlists for a channel' with a specific verb and resource, and is distinct from sibling tools like youtube_list_videos and youtube_create_playlist. It unambiguously communicates what the tool does.

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 usage is implied by the action 'List' and the parameters, but there is no explicit guidance on when to choose this tool over alternatives, nor any mention of exclusions or complementary tools. The agent must infer its use case from the name and sibling list.

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