bilibili_search_tool

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

With no annotations, the description carries full burden. It discloses that the tool returns video title, uploader, play count, danmaku count, etc., implying a read-only search operation. However, it does not explicitly state that the tool is non-destructive, nor does it mention any authorization requirements or rate 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?

The description is concise (two sentences) and front-loads the purpose. Every sentence adds value: what the tool does, sort options, and return fields. It could be slightly more structured, but overall 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?

Given the tool has an output schema (covering return values) and 3 parameters, the description provides adequate context: target platform, sort options, and return field highlights. It does not address pagination or result limiting, but the max_results parameter and output schema likely cover that.

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. It describes valid sort values (comprehensive, play count, newest, danmaku) and implies query is a search term, but does not mention max_results or clarify whether sort values map exactly to the parameter string. Coverage is partial; mores needed for max_results.

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 explicitly states the tool searches Bilibili videos (the target resource) and lists sort options and returned fields. It clearly distinguishes from sibling tools: baidu_search_tool (web search) and extract_chinese_page_tool (page extraction).

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 indicates the tool is for searching Bilibili content and specifies sort options, but lacks explicit guidance on when to use vs. alternatives or when not to use it. Context from sibling names provides some differentiation, but the description itself does not offer direct comparisons.

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