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

Beyond the annotations, the description discloses meaningful behavior: transcript is null when Rumble exposes no captions, no charge in that case, credits are consumed on success, and 'repeated requests may purchase data again' is a useful no-caching warning. The value is undercut by conflicting cost claims ('1 credit per request' vs 'at least 10 Nexscope credits'), which leaves the agent unsure of the real price.

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 sentence is well front-loaded, but the text then repeats the same paragraph twice and includes scraped page artifacts ('Rumble Transcript API View Pricing', '1 credit per request') plus two contradictory pricing blocks. Roughly half the content is duplicated boilerplate rather than information.

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 one-parameter, no-output-schema lookup, the description does cover the return shape (transcript or null) and the billing model, which is the important missing piece. However, the inconsistent credit figures and the truncated/duplicated pricing boilerplate leave the cost model ambiguous, which is the one thing an agent deciding to call it needs to know.

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?

There is a single parameter with 100% schema description coverage ('Rumble video URL'), so the schema already carries the semantics. The description adds nothing about accepted URL formats, canonical vs short links, or whether videos without captions should be pre-checked, so 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 opening sentence names a specific verb and resource — retrieving a Rumble video's transcript — and adds a real precondition ('when captions are available'). It is clearly distinguishable from siblings like social_rumble_video or social_rumble_video_comments, though it never names a sibling explicitly to route the agent.

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?

The 'when captions are available' condition and 'does not use AI transcription' hint at scope, but there is no explicit when-to-use vs when-not guidance and no alternative tool is named for cases where AI transcription or no captions is acceptable. Usage is implied rather than directed.

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