bilibili_hot

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

Annotations are absent, so description must disclose behavioral traits. It only states it 'gets' data, implying read-only, but does not explicitly confirm safety, side effects, or authorization needs. No mention of data freshness, rate limits, or result size limits.

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?

Single sentence front-loads the core purpose, including data fields. No unnecessary words. Could add structure like bullet points for clarity, but remains efficient.

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?

No output schema, no annotations. Description provides minimal context: it returns a list with specific metrics. Lacks details on pagination, error handling, or data format. For a simple tool with two optional params, this is borderline adequate but still leaves gaps.

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% as both parameters (max, page) have descriptions in the schema. The tool description adds no additional meaning beyond the schema. 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?

Description clearly states the tool retrieves current hot video list from Bilibili with data like play count, danmaku count, likes. It uses a specific verb '获取' and resource '热门视频列表', making purpose clear. However, it does not explicitly differentiate from sibling tools like bilibili_search_hot, which may also return hot videos.

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?

No guidance on when to use this tool versus alternatives. No mention of prerequisites, typical use cases, or exclusions. The description lacks context about when this tool is appropriate compared to other Bilibili tools.

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