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

Annotations already cover read-only and open-world behavior, and the description adds genuinely useful traits: fixed ordering (newest first), page size of 25, cursor-based continuation, and a cost of 1 credit. It stops short of describing failure modes or whether the full upload history is reachable.

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?

Four short sentences, front-loaded with the resource and ordering, then pagination mechanics, then cost. The opening sentence is redundant with the title, but everything after it 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?

For a simple read tool with readOnly/openWorld annotations this covers most needs, but with no output schema the description never hints at what an upload record contains, and cache_max_age is left entirely unexplained.

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 67%, so the schema documents handle formats and cursor adequately, and the description reinforces the cursor's paging role. The third parameter, cache_max_age, is undocumented in both the schema and the description, and no parameter meaning is added beyond what the schema states.

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 states the specific resource and scope: a Rumble channel's public uploads, ordered newest first. It is clearly distinguishable from siblings like rumble_video (single video), rumble_search (query-based) and rumble_comments, though the verb is implied rather than explicit and the first sentence only restates the title.

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?

Usage is implied: supply a channel handle to list its uploads, and pass the cursor from a previous response to continue paging. It never says when to prefer this over rumble_search or rumble_video, nor what happens for a channel with no uploads or an invalid handle.

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