Transcript

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

Goes well beyond the annotations: it discloses the paid-credit cost, the confirm=true prerequisite, the null-on-missing-captions outcome, and clarifies that these read-like POSTs do not publish to social platforms — which helpfully reconciles the readOnlyHint=false annotation.

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?

Three tight, front-loaded sentences that each carry distinct information (purpose, null behavior, cost/confirm). No filler, though the credit/publish caveats could be slightly compressed.

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 3-parameter tool with no output schema and full schema coverage, the description is nearly complete — it covers the failure mode (null), cost, and confirmation. Minor gaps remain around account selection behavior, but nothing essential is missing.

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%, so the schema already documents url, account, and confirm. The description adds only the confirm=true requirement, which is already stated in the schema, so baseline 3 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?

States a specific verb and resource — 'Gets a Rumble video's transcript' — and scopes it to Rumble, clearly distinguishing it from siblings like rumble_video, rumble_comments, and transcript tools on other platforms.

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?

Gives clear context for use: it returns a transcript when captions exist, returns null otherwise, and requires confirm=true. It stops short of naming an alternative or an explicit when-not-to-use-this-vs-sibling condition, so it lacks the routing language of a 5.

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