bili_search

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

No annotations are provided, so the description carries the full behavioral burden. "External data" vaguely suggests an external source, but the description does not disclose read-only behavior, rate limits, authentication requirements, pagination, result limits, or side effects. It adds little behavioral context beyond the basic purpose.

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 very short and front-loads the core action and resource. "External data." is a terse fragment that is less useful than the preceding sentence, but overall it avoids waste.

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?

An output schema exists, so return values need not be fully documented. However, with no annotations and 0% schema description coverage, the description should explain the keyword/num/order parameters and basic behavior; it does not, leaving the definition incomplete for correct invocation.

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% and there are three parameters, yet the description never mentions the required keyword parameter, the num default, or the order default. It lists returned fields instead of explaining parameter meaning, so it does not compensate for the schema's complete lack of parameter descriptions.

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: "Search real public videos," and lists the main returned fields (titles, BV IDs, UP authors, brief descriptions). It is clear what the tool does, but it does not distinguish itself from sibling tools such as bili_discover, bili_video_info, or bili_user_videos.

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 word "Search" implies usage for keyword-based video discovery, but the description gives no explicit when-to-use guidance, prerequisites, or alternatives. It does not explain when an agent should choose this over bili_discover, bili_browse_advance, or bili_video_info.

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