get_bilibili_favorites

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It explains the default behavior when uid is omitted and the login requirement, which is valuable. However, it does not disclose whether other users' favorites require authentication, how pagination behaves, or what happens if no favorites exist.

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 compact and front-loaded with the core purpose, followed by a short Args section. Every sentence earns its place and there is no filler.

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?

For a two-parameter getter, the description covers purpose, parameter behavior, defaults, and an auth caveat. An output schema exists for return details, so not describing in depth the response format is acceptable. Minor gaps remain around auth for public users and pagination size.

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%, but the description fully compensates for both parameters: uid's meaning and ownership behavior, and page's default, are explained. It adds genuine semantics beyond the bare schema types and defaults.

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 action ('Get') and a specific resource ('Bilibili user's favorite folders and videos'), clearly distinguishing it from sibling tools like get_bilibili_user_info or get_bilibili_following_list. The object of the operation is unambiguous.

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 gives practical context: if uid is not provided, it returns your own favorites and requires login. This helps the agent decide when to set uid versus omit it—but it does not explicitly mention alternatives or when not to use this tool.

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