youtube_channel_scraper

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that no API key or quota is needed and that billing goes through the user's Apify account at roughly $0.0005 per video, but it omits rate limits, error handling, and authentication requirements beyond billing.

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?

Two sentences with zero waste. The core purpose and returned fields are front-loaded, and the billing detail earns its place by setting cost expectations.

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?

There is no output schema, so listing returned fields (title, views, duration, publish time, thumbnail) is helpful. But with nine sibling tools, the description lacks the usage guidance and differentiation an agent needs to confidently select this tool over alternatives. The rich parameter schema compensates somewhat.

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 100%, so the input schema already documents all four parameters thoroughly, including enums and defaults. The description adds no parameter-specific syntax or meaning beyond what the schema provides, so the baseline of 3 applies.

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 (extracts) and resource (videos, Shorts or livestreams from any YouTube channel) plus the returned metadata fields. However, it does not explicitly distinguish itself from siblings such as youtube_channel_videos or youtube_search_scraper.

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 description explains what the tool does but gives no when-to-use guidance, prerequisites, or alternatives. It never mentions when to choose this over youtube_search_scraper or youtube_channel_videos.

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