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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the description's main added value is the response shape and the cost disclosure ('at least 10 Nexscope credits', 'repeated requests may purchase data again'). That cost information is genuinely useful for an agent budgeting calls, but it is internally inconsistent — the pasted block then says '1 credit per request' — which undermines confidence in the pricing claim.

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 core sentence is good, but it is buried under pasted vendor boilerplate: 'Rumble Channel Videos API View Pricing', a duplicated restatement of the opening sentence, and two conflicting credit figures ('at least 10 Nexscope credits' vs '1 credit per request'). Roughly half the text does not earn its place and actively confuses the cost signal.

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 helpfully enumerates the return payload, and it warns about credit consumption for a paid lookup. The critical gap is that all three parameters are optional — nothing states what happens if neither handle nor url is supplied — so an agent cannot tell whether a bare call is valid or errors.

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%, and each parameter already documents its alternative ('If you'd prefer to use the handle instead...'). The description only restates 'by handle or URL' and mentions the cursor as 'a numeric cursor for the next page', adding little beyond the schema; baseline 3 applies.

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 first sentence states a specific verb and resource ('Gets videos from a Rumble channel by handle or URL') and the second enumerates the response payload (channel metadata, videos, shorts, cursor), so the agent knows exactly what the tool returns. It does not, however, distinguish itself from nearby siblings such as social_rumble_search or social_rumble_video, so discrimination relies on the tool name.

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 only implied: 'by handle or URL' tells the agent which identifiers are accepted, and the mention of a next-page cursor hints at pagination flow. There is no explicit statement of when to choose this over social_rumble_search or social_rumble_video, and no exclusions or prerequisites are given.

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