bilibili_ranking

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds the rid=0 meaning (site-wide versus per-region), but says nothing about result size, pagination, or whether the ranking is a snapshot; with annotations carrying the load, a 3 fits.

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?

A single short clause, front-loaded with the [发现] category tag and the core action, with zero filler. It is terse to the point of under-specification, but nothing is wasted.

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 two-parameter read-only tool with full annotations and no output schema, the description covers the main axis (region) but omits any explanation of the `type` ranking variant, which an agent would need to choose a value confidently.

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 0%, so the description must compensate and only partially does: it explains rid (0 = site-wide) but leaves the `type` enum values (all / origin / rookie) completely undefined, which is the more ambiguous of the two parameters.

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+resource (读取排行榜 'read the ranking') with a scope qualifier (按分区 'by region'), which separates it reasonably well from siblings like bilibili_popular or bilibili_search_hot. It stops short of explicitly naming those alternatives.

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 indication of when to pick this over bilibili_popular (popular list) or bilibili_region_online (per-region activity), which are the obvious overlapping siblings. The only usage-like hint is the rid=0 note, which is really a parameter default rather than selection guidance.

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