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

With no annotations, the description carries the full behavioral disclosure burden. It only adds billing cost ('1 Credits') and a category label, but says nothing about auth, rate limits, return format, pagination, filtering, or whether the operation is read-only.

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 very short, but brevity replaces substance. 'Channel Videos Group: Channel' is redundant filler and does not earn its place, while the only useful detail is the per-call billing cost.

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?

This tool has 5 parameters, no annotations, and no output schema, yet the description provides almost no operational context. It fails to explain what channels/videos are returned, how cursor pagination works, what each filter value means, or what the response looks like.

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 0%, and the description adds no explanation for gl, hl, id, cursor, or filter. While the schema provides examples, a title for id, and an enum for filter, the description does not compensate for the missing parameter 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?

The description only restates the title ('Channel Videos Group: Channel.') and mentions billing cost; it never states a clear verb plus resource, such as 'Retrieves videos for a channel.' The function name hints at the purpose, but the text itself is essentially tautological.

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?

There is no guidance about when to use this tool versus alternatives like get_v1_channel_search or get_v1_channel_playlists. The description provides no context, exclusions, or alternative tool references.

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