bilibili_video_info

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

No annotations provided, so description must disclose behavioral traits. It only says what the tool returns, but does not mention side effects, authentication needs (e.g., cookie required), rate limits, or error behavior. For a read operation, it is implicitly non-destructive, but not explicitly stated.

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?

A single concise sentence in Chinese that front-loads the main purpose. Efficient and no wasted words, though could be slightly more structured by listing fields compactly.

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 one parameter and no output schema, the description is fairly complete for a simple info tool. However, it omits context on authentication (e.g., whether login/cookie is needed) and the structure of the output. Sibling tools suggest auth may be relevant.

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 is 100% covered with description for videoId (BV or avid). The tool description adds no extra detail beyond the schema, so baseline 3 is appropriate.

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 it gets detailed Bilibili video info and lists specific fields like title, play count, danmaku, etc. It is a specific verb+resource and distinguishes from siblings like bilibili_video_comments and bilibili_video_danmaku.

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?

No guidance on when to use this tool versus alternatives (e.g., vs. bilibili_video_comments or bilibili_video_danmaku). Does not mention when not to use it or any prerequisites.

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