search_youtube_channel_videos

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

Discloses that it uses the YouTube Search API, is quota-expensive (100 units per page), and results may be capped. Also explains pagination mechanism with page_token, adding value beyond no 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?

Well-structured with clear sections (purpose, when to use, important notes, pagination, returns). Each sentence adds value with no redundancy.

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?

Provides sufficient context for most aspects: purpose, usage, pagination, and return values. However, lacks parameter explanations for non-obvious fields, which is a minor gap.

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 description must compensate. It explains pagination tokens but does not describe other parameters like order, max_videos, parts_level, etc., leaving gaps.

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 it searches for videos within a channel by keyword, distinguishing it from sibling tools like list_youtube_channel_videos which enumerates the full playlist.

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?

Includes a 'When to use' section explicitly recommending this tool for keyword searches without enumerating the full uploads playlist, providing clear context for usage.

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