youtube_channel_search

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

No annotations exist, so the description carries the burden. It mentions 'normalized video search items' and 'resolved top-level query', hinting at output structure, but does not disclose rate limits, authentication needs, or any potential side effects. For a search tool, it's adequate but not detailed.

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 concise sentences that front-load the core purpose. No redundant or extraneous information. Every word earns its place.

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 no output schema and no annotations, the description is minimal. It explains the action and output style but omits details on pagination behavior, error scenarios, and the nature of 'normalized' items. Adequate but could be more 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?

Schema coverage is 100% and the parameters are well-described in the schema. The description adds no extra meaning to the parameters; the mention of 'normalized video search items' relates to output rather than input semantics. Baseline 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?

The description explicitly states 'Search within a YouTube channel' and 'returns normalized video search items scoped to a specific channel', clearly distinguishing it from siblings like 'youtube_search' (searches across YouTube) and 'youtube_channel_videos' (lists all videos without a query).

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 implies usage for channel-specific search but does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives. Context from sibling tools helps but the description itself lacks this clarity.

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