get_bilibili_video_info

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

No annotations are provided, so the description carries the full burden. It only says 'Get,' which implies a read operation, but it doesn't disclose authentication requirements, rate limits, or potential side effects. The description could be more explicit that this is a safe read-only operation, especially in the context of a Bilibili integration with many auth-related siblings.

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 brief and front-loaded with the purpose. The Args block adds a little detail but is somewhat redundant with the schema; still, it doesn't waste much space. The overall structure is efficient.

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?

The tool is simple (one parameter) and has an output schema, so return format is covered elsewhere. The description is adequate for basic invocation but omits usage boundaries and auth context, which would be helpful given the many sibling tools and the lack of annotations.

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 schema has 0% description coverage, so the description must compensate. It provides 'bvid: Bilibili video ID (BVID),' which clarifies that the parameter is a Bilibili video ID and adds meaning beyond the raw property name. However, it doesn't give format examples or constraints, so it only partially compensates.

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 'Get detailed information about a Bilibili video,' which is a specific verb and resource. It clearly identifies the platform (Bilibili) and what action it performs, distinguishing it from sibling tools like search_bilibili_videos or get_bilibili_user_videos even without naming them.

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 use when you have a bvid and need detailed video information, but it doesn't explicitly state when to use this tool over alternatives, nor does it provide exclusions or prerequisites. There's no mention of searching vs. fetching a specific video, which is left to inference.

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