list_channel_videos

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

With no annotations, the description carries the transparency burden. It discloses the channel selection behavior (using channelId for Brand Accounts, otherwise the authenticated channel) and lists the returned data fields. This adds meaningful context beyond the schema, though it doesn't mention pagination or rate limits.

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?

The description is three short sentences, with the core purpose front-loaded, followed by important usage detail. Every sentence contributes essential information without 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?

For a tool with 3 optional parameters and no output schema, the description covers the essential aspects: what it returns, how to specify the channel, and the default behavior. It is complete enough for an agent to select and invoke the tool correctly without ambiguity.

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 the baseline is 3. The description adds value by providing a concrete example for channelId (UC_x33Gz4LvnOZuC_4v7Qucg for @dewtech) and explaining its purpose for Brand Accounts, which goes beyond the schema's basic description.

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 the tool lists videos from a YouTube channel with specific fields (title, views, likes, publication date). It uses a specific verb ('Lista') and resource ('vídeos de um canal YouTube'), and implicitly distinguishes from siblings by focusing on video listing rather than analytics or keyword tools.

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 guidance on when to use channelId (for Brand Accounts) and explains the fallback to the authenticated channel when channelId is omitted. While it doesn't explicitly name alternative tools, the context makes its usage clear, and no exclusions are mentioned.

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