实时数据/B站热榜

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description provides zero information about what this tool actually does behaviorally - whether it fetches, displays, filters, or processes the Bilibili hot list data. It doesn't indicate if this is a read operation, whether it requires authentication, what format the data comes in, or any other behavioral characteristics.

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?

While technically concise (just the tool name repeated), this is under-specification rather than effective conciseness. The description doesn't communicate any useful information in its minimal form. A truly concise description would still convey the tool's purpose and basic operation, which this completely fails to do.

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 apparent purpose (fetching Bilibili hot list data), the lack of annotations, no output schema, and the presence of many similar sibling tools, this description is completely inadequate. It provides no information about what the tool returns, how it behaves, or how it differs from alternatives. For a data-fetching tool in a crowded namespace, this minimal description fails to provide the necessary context.

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 tool has zero parameters, and the schema description coverage is 100% (though with no parameters, this is trivial). The description doesn't need to explain parameters since there are none. However, it also doesn't mention that this is a parameterless tool, which could be slightly helpful context. Given the zero-parameter baseline, this earns a 4 rather than a perfect 5.

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?

Tautological: description restates name/title.

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 description provides absolutely no guidance about when to use this tool versus its many alternatives. With 15 sibling tools that all appear to provide hot lists from different platforms (微博热搜, 抖音热榜, 知乎热榜, etc.), the agent has no information about why one would choose the Bilibili hot list over any other platform's hot list. There's no context about use cases, prerequisites, or differentiation.

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