youtube_channel

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

No annotations provided, so description carries full burden. Discloses endpoint sharing, ID format requirement, and provides detailed return structure. Missing behavioral details like error handling, rate limits, or consequences of invalid input, but the return structure adds significant 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?

Description is front-loaded with main action ('Scrapes comprehensive YouTube channel data') followed by credits, endpoint note, ID requirement, and return structure. Fairly concise but includes a long JSON example; could be slightly tighter but still well-structured.

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?

No output schema, but description provides a full, nested return structure with field details, credits, and endpoint notes. This compensates for the missing schema and gives complete context for an agent to understand what the tool returns and how to use it.

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 100%, so baseline is 3. Description adds value by clarifying that channel_id must be UC-prefixed (not a handle) and that it selects Channel behavior. Also notes defaults for country and language from schema, though no major extra beyond 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?

Description clearly states it scrapes comprehensive YouTube channel data including about info, subscriber counts, video sections, and Shorts. Distinguishes from sibling tools like youtube_search and youtube_video by focusing on channel data, and specifies it requires UC-prefixed channel ID, not a handle.

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?

Provides clear context: requires UC-prefixed channel ID, presence of channel_id selects Channel behavior on shared /youtube endpoint, and credits cost. However, does not explicitly state when not to use this tool versus alternatives like youtube_search or youtube_video, nor mention exclusions or prerequisites beyond the ID format.

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