Youtube.Videos.List

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

No annotations are provided, so the description carries the full behavioral burden. 'List' implies a read, but it says nothing about quota cost, maximum ids per call, whether private/unlisted videos require OAuth scope, or error behavior on invalid ids — all material for a YouTube Data API call.

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?

One front-loaded sentence with zero filler and the resource scope stated before the parenthetical source. Its brevity borders on under-specification, which keeps it from a 5.

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?

An output schema exists, so return values need no explanation, and the tool has only one parameter, which lowers the bar. Still, with no annotations the description should cover batch limits and auth/quota expectations for an agent to call it correctly.

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 0%, so the description must compensate. It does add meaning by characterizing video_ids as a 'batch' of ids rather than a single id, but gives no maximum batch size, id format, or behavior for unknown ids.

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?

States a specific verb (list) and resource (full video resources) and scopes it to a batch of video ids, which distinguishes it from siblings like youtube.channel.get or youtube.playlist_items.list. It does not explicitly name those siblings or explain the boundary, keeping it below a 5.

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?

There is no when-to-use guidance and no exclusions. The agent is not told when to prefer this over youtube.channel.get, youtube.playlist_items.list, or youtube.analytics.query when it already has ids versus when it needs discovery.

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