list_bilibili_favorite_videos

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

With no annotations, the description carries full burden. It discloses pagination behavior (bounded page, cursor traversal), authentication requirement (logged-in Bilibili Cookie), and a useful pointer for credential setup. It lacks details on error scenarios or rate limits, but covers essential behavioral expectations.

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 three sentences, front-loaded with the main purpose. Every sentence adds essential information (purpose, pagination guidance, credential note). No redundant or filler words.

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 an output schema exists (so return format is covered), the description sufficiently explains pagination, authentication, and prerequisite help. It is complete for an agent to effectively use this tool.

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 100% for the cursor parameter, so the schema already documents it. The description adds meaning by explaining that the cursor is an opaque token encoding a versioned Folder ID and page number, and that it never contains credentials or other data. This goes beyond the schema's basic description.

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 clearly states the tool's action ('Discover every created Favorite Folder... return one bounded page of its Video memberships') and resource (Favorite Folders and Video memberships). It effectively distinguishes this from sibling tools like search_bilibili_videos by focusing on listing favorite videos via pagination.

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 provides clear usage guidance: follow next_cursor until absent to traverse all folders, and do not assume a single response contains the full account. It also directs users to get_credential_setup_instructions for credential help. However, it does not explicitly state when NOT to use this tool or suggest alternatives.

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