bilibili_search

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

With no annotations, the description carries full burden. It discloses that totalrank does not sort by time and that the latest episode may not appear on page 1. This is a critical behavioral trait. It does not mention rate limits or other aspects, but the given information is valuable.

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 concise with two clear sentences. It front-loads the core purpose and then provides crucial behavioral context. No unnecessary words.

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?

While the description covers the most important nuance (ordering), it does not mention pagination behavior, duration filter, or the general structure of results. Given no output schema, some guidance on return format would improve completeness. Still, it addresses key usage concerns.

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 coverage is 100%, so parameters are well-documented. The description adds meaning beyond the schema by explaining the implication of the 'totalrank' order (not time-sorted), which is not in the parameter description. This helps the agent make better choices.

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 clearly states '搜索 B站视频' (search Bilibili videos), specifying the verb and resource. It distinguishes from sibling bilibili_user_videos by suggesting an alternative workflow for finding latest videos by a specific UP主. However, it does not explicitly differentiate from bilibili_search_hot.

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 explicitly advises when to use this tool: for general search of Bilibili videos, and when not: for finding latest videos of a specific UP主, recommending bilibili_user_videos instead. It also warns about the totalrank ordering behavior.

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