Fetch Bilibili search-box suggestion phrases for partial text; an unmatched query returns an empty suggestion list. Use it while composing a query, not when you need video records.
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | Required. Partial Bilibili search text. |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | The tool result payload (shape varies per tool; see each tool's docs resource). |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds a genuine behavioral detail beyond annotations: an unmatched query returns an empty suggestion list, which tells the agent how to interpret a null/empty result. It doesn't cover result ordering or limits, so it stops short of 5.
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?
Two sentences, zero filler, purpose front-loaded ahead of the usage constraint and the empty-result edge case. Every clause earns its place.
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?
Output schema exists, so return values need no explanation. Purpose, usage, and the empty-result edge case are all covered for a simple one-param lookup tool; nothing an agent needs to call it correctly is missing.
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?
Only one parameter, and the schema documents it fully ('Required. Partial Bilibili search text.') at 100% coverage. The description's 'partial text' phrasing matches the schema without adding format, length, or language constraints. Baseline 3 applies when the schema does the heavy lifting.
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 ('Fetch') and resource ('Bilibili search-box suggestion phrases') with scope ('for partial text'), and explicitly distinguishes itself from record-returning tools ('not when you need video records'). An agent can tell it apart from bilibili_popular/ranking/etc. without opening any schema.
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?
Gives both positive guidance ('use it while composing a query') and an explicit exclusion ('not when you need video records'). The when/when-not pair is unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
