Bottube Trending

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

No annotations are provided, so the description carries the full behavioral burden. The verb 'get' implies a read-only list operation, which is a useful signal, but the description does not clarify pagination, recency, or whether any side effects occur. For a simple read with an output schema, this is acceptable but not richly transparent.

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 description is one concise sentence with no filler. The key resource and verb are front-loaded, making it easy to scan and parse quickly.

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?

Given the tool's simplicity—one optional parameter, an output schema, and a read-only intent—the description plus schema is mostly sufficient for invocation. The only notable gap is the lack of usage guidance relative to sibling BoTTube tools.

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?

The schema already fully documents the single 'limit' parameter, including default and max values, so the description does not need to add parameter details. With 100% schema coverage, the baseline of 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?

The description uses a specific verb ('Get') and a specific resource ('trending videos on BoTTube'), making the operation unambiguous. It also differentiates from sibling tools like bottube_search and bottube_upload by focusing on the trending feed.

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 guidance on when to use this tool versus alternatives such as bottube_search or bottube_stats, nor any conditions/exclusions. The agent must infer from the word 'trending' alone that this is for the trending list rather than search or statistics.

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