Server Quality Checklist

Tool Scores

• enrich_webC
  2.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 carries the full burden of behavioral disclosure. It mentions the tool enriches context with web content but fails to describe key behaviors such as how it sources content, potential rate limits, authentication needs, or what the output looks like. This leaves significant gaps for a tool that presumably performs web queries.

  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, efficient sentence with no wasted words. It's front-loaded with the core purpose, though it could be more structured by explicitly separating purpose from constraints. Overall, it's appropriately sized for the minimal information it conveys.

  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 the tool's complexity (web content enrichment), lack of annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't explain the enrichment process, output format, or error handling, leaving the agent with insufficient information to use the tool effectively beyond a basic understanding.

  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?

  The schema has 0% description coverage, so the description must compensate. It doesn't mention the 'query' parameter at all, providing no semantic meaning beyond what the schema's pattern hint suggests (1-3 words). This is inadequate for a tool with one required parameter, as the agent lacks context on what constitutes an effective query.

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

  Purpose3/5

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

  The description states the tool 'enrich context with web content' which provides a general purpose (verb+resource), but it's vague about what specific type of enrichment occurs and how it differs from sibling tools like 'enrich_news'. The phrase 'focused on general, non-commercial web content' adds some differentiation but remains broad and non-specific.

  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?

  The description provides no explicit guidance on when to use this tool versus alternatives like 'enrich_news' or 'ask_fastgpt'. It mentions 'general, non-commercial web content' which implies a context but doesn't specify use cases, exclusions, or prerequisites, leaving the agent with minimal direction.

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

• enrich_newsC
  2.6/5.0
  Behavior2/5

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

  With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the content focus ('non-commercial news and discussions') which adds some context, but fails to describe critical behaviors: what 'enrich' means operationally, what format the enrichment takes, whether this is a read-only or write operation, potential rate limits, authentication needs, or error conditions. The description is insufficient for a tool with zero annotation coverage.

  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 extremely concise at just one sentence with zero wasted words. It's front-loaded with the core purpose and efficiently adds domain specificity. Every word earns its place, making this a model of brevity.

  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 the tool has no annotations, no output schema, and 0% schema description coverage, the description is incomplete. While concise, it fails to provide sufficient information about what the tool actually does operationally, what results to expect, or how to use it effectively. For a tool with such sparse structured data, the description should do much more heavy lifting.

  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%, so the description must compensate for the undocumented parameter. The description mentions 'web content focused on non-commercial news and discussions' which implies the 'query' parameter should relate to this domain, but provides no specifics about what constitutes appropriate queries, expected formats, or how the query influences results. The single parameter remains poorly defined despite the description's attempt at context.

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

  Purpose3/5

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

  The description states the tool 'enrich context with web content' which provides a general purpose, but lacks specificity about what 'enrich' means operationally. It mentions 'focused on non-commercial news and discussions' which adds some domain context, but doesn't clearly distinguish this tool from its sibling 'enrich_web' or explain what makes it unique. The purpose is understandable but vague.

  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?

  The description provides no guidance on when to use this tool versus alternatives. It doesn't mention the sibling tools 'ask_fastgpt' or 'enrich_web', nor does it provide any context about appropriate use cases, prerequisites, or limitations. The agent receives no help in selecting between available tools.

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

• ask_fastgptC
  2.7/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 the full burden. It mentions that the tool searches the web and provides answers with references, which gives some behavioral context. However, it lacks details on permissions, rate limits, response format, or potential side effects, leaving significant gaps for a tool that interacts with external resources.

  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, efficient sentence that front-loads the core functionality. It avoids unnecessary words, but could be slightly improved by structuring it to highlight key actions more clearly.

  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 the complexity of a web search tool with no annotations, no output schema, and low parameter coverage, the description is incomplete. It lacks details on error handling, response structure, or integration with siblings, making it inadequate for reliable agent use.

  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?

  The input schema has one parameter ('query') with 0% description coverage. The description adds minimal semantics by implying the query is for web search, but it doesn't specify format, length, or examples. With low schema coverage, the description doesn't adequately compensate, leaving the parameter poorly documented.

  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's purpose: 'Ask fastgpt to search web and give an answer with references.' It specifies the verb ('ask'), resource ('fastgpt'), and outcome ('answer with references'). However, it doesn't explicitly differentiate from sibling tools like 'enrich_news' or 'enrich_web' beyond implying web search functionality.

  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?

  The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools or contexts where this tool is preferred, such as for general web queries versus news-specific enrichment. Usage is implied by the description but not explicitly stated.

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