Server Quality Checklist

Tool Scores

• parse_bilibili_videoC
  2.9/5.0
  Behavior2/5

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

  With no annotations provided, the description carries the full burden of behavioral disclosure. It does not state that the tool is read-only, makes network requests, or any rate limits or side effects. The description only says it 'parses' and 'gets' information, leaving key behavioral aspects undisclosed.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness4/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, concise sentence that front-loads the main purpose and lists key output fields. It contains no redundant information, though it could benefit from a more structured breakdown.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness3/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  There is no output schema, so the description must explain return values. It mentions several important fields (title, cover, video link, user info, collection playlist) but doesn't detail the structure or any edge cases. Given the tool's low complexity, this is adequate but leaves room for improvement.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The schema already provides 100% coverage for the single 'url' parameter, including support for b23.tv short links and full links. The description doesn't add extra meaning beyond what the schema offers, so the baseline of 3 applies.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose4/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states it parses Bilibili video links and retrieves complete video information, listing specific fields like title, cover, video link, user info, and collection video list. It distinguishes itself as a comprehensive parser, but doesn't explicitly name sibling tools as alternatives.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  No guidance is provided on when to use this tool versus sibling tools like get_bilibili_video_info or get_bilibili_collection. The description lacks any context about preferred use cases or prerequisites.

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

• get_bilibili_basic_infoB
  3.1/5.0
  Behavior2/5

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

  Annotations are absent, so the description carries the full burden of behavioral disclosure. It lists output fields but does not explicitly state read-only nature, side effects, authentication needs, or error behaviors. The verb "获取" implies read-only but is not explicit.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single sentence that is direct and informative, front-loading the action and primary resource. No wasted words.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness3/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  For a simple one-parameter tool with no output schema, the description covers the basic purpose and output fields. However, it does not disambiguate from sibling tools or explain the return format fully, making it only partially complete.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The schema description coverage is 100% for the single 'url' parameter. The tool description adds no extra parameter meaning beyond what the schema already provides, so the baseline of 3 applies.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose4/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the tool gets basic Bilibili video info, listing specific fields (title, cover, description, user info). However, it does not distinguish from the similarly named sibling 'get_bilibili_video_info', so it lacks differentiation.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  No guidance is provided on when to use this tool vs. alternatives such as parse_bilibili_video or get_bilibili_video_info. There are no exclusions, prerequisites, or alternative references.

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

• get_bilibili_collectionB
  3.3/5.0
  Behavior2/5

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

  No annotations are provided, and the description does not disclose behavioral traits such as output format, pagination limits, authentication requirements, or side effects. It simply describes a read operation without additional context.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, concise sentence that communicates the core purpose without unnecessary words. It is front-loaded and easy to understand.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness3/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  For a simple tool with one parameter and no output schema, the description is minimally viable but lacks details about the return format, potential limitations, or prerequisites. The absence of annotations and output schema means the description should carry more weight, but it remains somewhat incomplete.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The schema description covers 100% of the single parameter (url) by explicitly stating it is a Bilibili collection link. The tool description adds no extra semantic meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states that the tool retrieves all video list information from a Bilibili collection. It uses a specific verb (获取/get) and resource (Bilibili 合集), distinguishing it from sibling tools that focus on single video parsing, info, or download URLs.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  No guidance is provided on when to use this tool versus alternatives like get_bilibili_video_info or parse_bilibili_video. The description only states what the tool does, without any exclusions or context for choosing it.

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

• get_bilibili_download_urlsA
  3.5/5.0
  Behavior2/5

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

  No annotations are provided, so the description carries full behavioral burden. It only states the action and a feature, but does not disclose authentication requirements, return format, potential large responses for collections, error handling, or any side effects. This is a minimal disclosure that leaves significant behavioral unknowns.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, focused sentence that front-loads the primary action. It avoids unnecessary fluff and every phrase adds value, making it appropriately concise and well-structured.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness3/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the simple one-parameter schema and no output schema, the description gives the basic purpose but omits details about the returned download link list (e.g., format, quality options, ordering) and error behavior. It meets the minimum viable standard but has clear gaps for an agent to use it confidently without further inference.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 100% for the 'url' parameter, which is described as 'Bilibili 视频链接'. The tool description adds the collection video support, but does not clarify whether the URL must be a collection URL or how collection handling affects the parameter. Baseline is 3 because the schema handles parameter meaning, but no extra semantic depth is added.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the tool's function: '获取 Bilibili 视频的下载链接列表' (get the list of download links for Bilibili videos). It uses a specific verb and resource, and mentions support for collection videos, which distinguishes it from sibling tools focused on parsing, info, or basic info.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines3/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description implies usage (to retrieve download links) and notes support for collection videos, but does not explicitly state when to use this tool versus siblings like get_bilibili_video_info or get_bilibili_collection. No exclusions or alternatives are provided.

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

• get_bilibili_video_infoA
  3.8/5.0
  Behavior3/5

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

  With no annotations provided, the description must carry the full burden of behavioral disclosure. It describes what information is retrieved (title, cover, etc.) and, by using '获取' (get), implies a read-only operation with no side effects. However, it does not mention error behaviors, authentication requirements, rate limits, or any potential side effects. The transparency is adequate for a simple info retrieval but lacks deeper behavioral context.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, concise sentence that front-loads the main action ('获取 Bilibili 视频的详细信息') and then provides a list of example data fields. Every word earns its place, with no redundancy or fillers. It is appropriately sized for a tool with one parameter and simple purpose.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the low complexity (1 parameter, no output schema, no annotations), the description is fairly complete. It lists key return elements (title, cover, introduction, user info, video list) with an 'etc.' to indicate more. It differentiates from siblings like 'basic info' and 'download URLs', providing enough context for an agent to understand the tool's place. A minor gap is the lack of explicit return format, but the field list offers sufficient clarity for this simple tool.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The input schema already describes the only parameter 'url' with 'Bilibili 视频链接' (Bilibili video link), achieving 100% schema description coverage. The description does not add extra meaning about the parameter format, constraints, or how the URL should be crafted. Since the schema fully covers the parameter, the added value from the description is minimal, aligning with the baseline score of 3.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the tool's purpose: '获取 Bilibili 视频的详细信息' (Get detailed Bilibili video information) and enumerates specific data fields (title, cover, description, user info, video list). This makes it distinct from siblings like 'get_bilibili_basic_info' (basic info) and 'get_bilibili_download_urls' (download URLs), establishing a unique resource and granularity.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines3/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description implies usage context by specifying 'detailed information' in contrast to sibling 'basic info', but it does not explicitly state when to use this tool versus alternatives or provide exclusions. There is no direct guidance on prerequisites or conditions, making the usage guidance implicit rather than explicit.

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