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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only mentions billing per call, which is a minor detail, but does not disclose any behavioral traits such as side effects, data returned, or limitations. It is completely inadequate for a tool that likely performs a read operation on channel videos.

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 extremely short, but it is under-specified rather than concise. It lacks essential information. The sentence 'Channel Videos Group: Channel. Billing per call: 1 Credits.' is not structured to front-load useful information; it is just a label and a billing note. It does not earn its place as a meaningful description.

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 the tool's complexity (nested object parameter, no output schema, no annotations), the description is completely inadequate. It does not explain what the tool returns, how to use the 'body' parameter effectively, or any behavioral context. The sibling tools suggest a rich API, but this description provides no completeness.

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?

The schema has one parameter 'body' with a description that includes an example JSON. The schema description coverage is 100% because the 'body' parameter is described with an example. However, the description does not add any additional meaning beyond the schema. The example provides some context, but the tool description itself does not explain the parameters. Since the schema covers the parameter, the baseline is 3, but the description adds no value, so a 2 is appropriate.

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 'Channel Videos Group: Channel. Billing per call: 1 Credits.' is vague and does not clearly state what the tool does. It mentions 'Channel Videos' but lacks a specific verb or resource description. The sibling tool 'get_v1_channel_videos' likely has a similar purpose, and this description does not distinguish itself. The title 'Channel Videos' is repeated, making it close to a tautology.

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 on when to use this tool versus alternatives. The description provides no context about use cases, prerequisites, or exclusions. The sibling tools include 'get_v1_channel_videos' which likely overlaps, but no differentiation is provided.

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