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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description usefully adds that lookups consume at least 10 credits, that cost varies by options, and that repeated requests may re-purchase data — real behavioral value beyond the annotations. However, the cost text is self-contradictory ("at least 10 Nexscope credits" vs "1 credit per request" and "Examples are not guaranteed prices"), which leaves the agent unsure of the actual charge.

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 first two sentences are well front-loaded and informative, but they are followed by a wall of pricing boilerplate that repeats the purpose sentence verbatim and mixes conflicting credit figures. Roughly half the text is redundant or contradictory vendor boilerplate that does not help an agent act.

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 compensates by enumerating the return fields (title, URL, thumbnail, channel, published date, view counts, cursor), and it discloses the credit cost model. Still missing are result-count limits and any note on how many pages are retrievable, minor gaps for a simple two-parameter search.

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 100%, so both parameters are already documented, including the cursor semantics ("the next page number, like 2 or 3"). The description's mention of a "numeric cursor for the next page" merely restates the schema, so baseline 3 applies with no added meaning.

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 opening sentence gives a specific verb and resource ("Searches Rumble videos by keyword") and the scope is narrow enough to separate it from channel- or video-level siblings such as social_rumble_channel_videos and social_rumble_video. It never names an alternative explicitly, and the purpose statement is redundantly repeated after the pricing boilerplate, which blunts an otherwise clear statement.

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 when-to-use or when-not-to-use guidance and no mention of alternatives among the many Rumble siblings. Nothing tells the agent to prefer this over a channel lookup when it already knows the channel, nor any guidance on paginating via cursor.

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