Fetch Bilibili's anonymous Guochuang (Chinese animation) homepage sections, including featured titles, updates, schedule, ranking, and recommendations. Use bilibili_anime_home for general anime or bilibili_ranking and bilibili_must_watch for focused charts.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| 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 meaningful context beyond them: the endpoint is 'anonymous' (no auth required) and enumerates the section categories returned. No pagination or rate-limit detail, but that is minor given annotations.
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, no filler. The scope statement is front-loaded and the sibling routing follows it, which is the correct ordering for selection decisions.
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-value explanation is not required, and annotations cover the safety profile. The description is complete enough to select and call the tool correctly; only minor behavioral detail (ordering/refresh cadence of homepage sections) is absent.
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?
The tool takes zero parameters, so the baseline is 4. The description correctly adds no parameter guidance because none is needed, and the content-type list gives a sense of the shape without overreaching.
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 a precisely scoped resource ('Bilibili's anonymous Guochuang homepage sections'), then enumerates the section types returned. It explicitly names competing siblings (bilibili_anime_home, bilibili_ranking, bilibili_must_watch), so an agent can distinguish it without opening the 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?
Routes the agent to alternatives by audience/purpose: bilibili_anime_home for general anime, bilibili_ranking and bilibili_must_watch for focused charts. This is strong alternative guidance, but the 'when to use this tool' case is left implicit rather than stated outright.
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.
