bilibili_ranking

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

With no annotations, the description carries the full behavioral burden. It discloses what will be returned (ranking with video engagement, category, creator metadata) and their rank order, but it does not disclose limitations such as pagination, ranking size/truncation, update frequency, or any caveats about the current snapshot.

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 two sentences and mostly efficient. The second sentence partly restates the first ('...all-site ranking' appears twice), but overall it adds meaningful detail about metadata fields and ordering without unnecessary filler.

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 zero-parameter no-output-schema tool, the description covers the key points: what data is returned, its metadata components, and that results are ordered by rank. A minor gap is the absence of any mention of the exact number of items or whether the list is paginated, but for a simple ranking endpoint the description is reasonably complete.

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, so the baseline is 4. The description does not need to add parameter detail; both schema and description agree there is nothing to pass. It correctly focuses on the output rather than inputs.

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 states a specific verb and resource: 'Get the current Bilibili all-site ranking' and clarifies the result scope as the 'official all-site ranking'. It also differentiates from sibling tools like bilibili_weekly, bilibili_popular, and bilibili_must_watch by emphasizing it is the all-site, official ranking, which is a clear distinguishing feature.

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 implies usage context through 'current' and 'all-site' but never explicitly names alternatives or states when not to use this tool. Sibling tools like bilibili_weekly and bilibili_popular exist, and an agent must infer when ranking is preferable to those, so the guidance is only implicit.

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