list_channel_videos

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds the pagination contract (cursor pass-through) which is genuinely useful beyond the annotations, but says nothing about ordering, rate limits, or the shape of the returned listing.

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 short sentences, front-loaded with the core purpose and followed by the one operational rule that matters. No filler and nothing buried.

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?

With no output schema, the description should characterize what 'the listing' contains (video IDs, titles, ordering, page metadata), but it only says it returns 'the listing'. Parameters and annotations are otherwise sufficient for correct invocation.

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 limits, cursor opacity, channel formats, and timeout defaults are already documented, warranting the baseline 3. The cursor sentence echoes the schema's 'Opaque cursor from a previous call' rather than adding new semantics.

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 and resource ('List videos from one YouTube channel') with clear scope, so an agent knows it retrieves a channel's video listing. It never names or distinguishes itself from close siblings such as get_channel_latest_videos or search_channel_videos, so the boundary is left implicit.

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 sentence 'Pass cursor unchanged for the next page' gives concrete pagination usage, but there is no guidance on when to choose this over get_channel_latest_videos or search_channel_videos, nor any stated prerequisites or exclusions. Usage is implied by the scope wording only.

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