Server Quality Checklist

Tool Scores

• baidu_search_toolB
  3.4/5.0
  Behavior2/5

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

  No annotations are provided, so the description must fully disclose behavior. It mentions '实时信息' (real-time info) but lacks details on pagination, rate limits, result format, or any destructive/read-only nature. The behavioral description is insufficient.

  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 brief (two sentences), front-loaded with the action. It could include more detail without becoming verbose, but it is well-structured and avoids redundancy.

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

  Completeness2/5

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

  Given no annotations, no parameter explanations, and unknown output schema details (though output schema exists), the description is incomplete. Missing behavioral traits, parameter guidance, and result handling information.

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

  Parameters2/5

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

  Schema has 2 parameters (query, max_results) with no descriptions (0% coverage). The description does not explain parameter usage, defaults, or constraints. It should compensate but does not, leaving the agent to infer.

  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 verb '搜索' (search) and resource '百度网页' (Baidu web pages), with purpose '获取中文互联网的实时信息' (get real-time info from Chinese internet). It distinguishes from siblings: bilibili_search_tool (video) and extract_chinese_page_tool (page extraction).

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

  Usage Guidelines4/5

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

  The description lists suitable use cases: '适合查找中文网站、新闻、百科、技术文章等' (suitable for finding Chinese websites, news, encyclopedia, tech articles), providing context on when to use. However, it does not explicitly state when not to use or offer alternatives.

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

• bilibili_search_toolA
  3.7/5.0
  Behavior3/5

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

  With no annotations, the description carries full burden. It discloses that the tool returns video title, uploader, play count, danmaku count, etc., implying a read-only search operation. However, it does not explicitly state that the tool is non-destructive, nor does it mention any authorization requirements or rate limits.

  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 concise (two sentences) and front-loads the purpose. Every sentence adds value: what the tool does, sort options, and return fields. It could be slightly more structured, but overall efficient.

  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 tool has an output schema (covering return values) and 3 parameters, the description provides adequate context: target platform, sort options, and return field highlights. It does not address pagination or result limiting, but the max_results parameter and output schema likely cover that.

  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 0%, so the description must compensate. It describes valid sort values (comprehensive, play count, newest, danmaku) and implies query is a search term, but does not mention max_results or clarify whether sort values map exactly to the parameter string. Coverage is partial; mores needed for max_results.

  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 explicitly states the tool searches Bilibili videos (the target resource) and lists sort options and returned fields. It clearly distinguishes from sibling tools: baidu_search_tool (web search) and extract_chinese_page_tool (page extraction).

  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 indicates the tool is for searching Bilibili content and specifies sort options, but lacks explicit guidance on when to use vs. alternatives or when not to use it. Context from sibling names provides some differentiation, but the description itself does not offer direct comparisons.

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

• extract_chinese_page_toolA
  4.1/5.0
  Behavior4/5

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

  Discloses key behavior of removing ads and navigation interference. With no annotations provided, the description fulfills transparency for a read-like operation, though it could mention if any authentication is needed.

  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?

  Two sentences efficiently convey purpose, suitable sites, and behavior. No redundant information.

  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?

  Description covers what the tool does, for which sites, and what it removes. With an output schema present, lack of return value details is acceptable. Could mention that results are in Chinese.

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

  Parameters2/5

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

  Schema description coverage is 0%, and the description only mentions URLs should be from Chinese web pages, but does not add constraints like required format, encoding, or examples for the 'url' parameter.

  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?

  Description clearly states the tool extracts main text from Chinese web pages, with specific examples (Zhihu, Bilibili, 36kr, CSDN) that distinguish it from search-focused siblings like baidu_search_tool and bilibili_search_tool.

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

  Usage Guidelines4/5

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

  Explicitly states it is 'suitable for reading' content from Chinese websites, indicating when to use. While it doesn't specify when not to use, the context of siblings suggests it's for extraction rather than searching.

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