bilibili_video_favorite

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false and openWorldHint=true, so the write/destructive profile is fully covered in structured data; the description's [互动写入] merely restates it. It adds no extra context about the confirmation flow, the effect of simultaneous add/del in one call, or any rate-limit/permission behavior.

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?

One compact sentence with the write nature front-loaded and the comma-separated format detail attached directly to the folder-ID concept. No filler, though the sentence is arguably too short given the tool's complexity.

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?

There is no output schema, and for a destructive, non-idempotent write with five parameters the description omits what the tool returns and how add/del combine in a single call. The 20% schema coverage leaves several parameters undocumented in both places, so the definition is only marginally complete.

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 only 20%, so the description must carry weight; '夹ID以逗号分隔' usefully explains the format of add_media_ids/del_media_ids, which the schema leaves bare. However, it says nothing about rid (the video ID), the type field, or how add and del interact, so the compensation is only partial.

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 pair (add/remove from a favorite folder) and resource, and signals the write nature with the [互动写入] tag. This distinguishes it from read siblings like bilibili_favorite_items and from other write siblings like bilibili_watch_later_add, though it never names an alternative explicitly.

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 implies usage (managing a favorite folder's contents) but gives no when-to-use/when-not guidance, no mention of the confirm gate or --enable-writes prerequisite (these live only in the schema), and no pointer to a sibling such as bilibili_favorite_folders for discovering folder IDs.

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