Server Quality Checklist

Tool Scores

• get_template_detailA
  4.1/5.0
  Behavior3/5

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

  With no annotations provided, the description carries full burden. It discloses that the tool returns '模板的完整内容' (complete template content) and mentions error behavior: '如果模板不存在，会返回明确的错误信息' (if template doesn't exist, returns clear error message). However, it doesn't describe authentication needs, rate limits, or other behavioral traits like response format or performance characteristics.

  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 efficiently structured with four sentences that each serve distinct purposes: stating the core function, specifying parameter requirements, describing the return value, and explaining error behavior. There's no wasted text, and key information appears early.

  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?

  For a single-parameter read operation with no annotations and no output schema, the description provides good coverage: purpose, parameter constraints, return value description, and error behavior. However, it doesn't fully explain what '完整内容' (complete content) includes or the response format, leaving some ambiguity about the output.

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

  Parameters4/5

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

  Schema description coverage is 100%, so the baseline is 3. The description adds meaningful context about the templateName parameter: it must come from get_template_list responses and ensures '参数的准确性和一致性' (parameter accuracy and consistency). This provides practical usage guidance beyond the schema's technical description, elevating the score.

  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: '获取指定模板的详细内容' (Get detailed content of a specified template). It specifies the verb ('获取' - get) and resource ('模板的详细内容' - template details). However, it doesn't explicitly differentiate from its sibling tool 'get_template_list' beyond mentioning that templateName must come from that tool's response.

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

  Usage Guidelines5/5

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

  The description provides explicit usage guidance: 'templateName 参数必须使用 get_template_list 返回的 templates 中的 templateName 值' (templateName parameter must use the templateName value from templates returned by get_template_list). It clearly states when to use this tool (to get template details) and references the alternative/sibling tool for obtaining valid parameter values.

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

• get_template_listA
  4.6/5.0
  Behavior4/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 effectively describes the tool's behavior: it returns structured data with specific fields (templateName, filename, description), explains the output format (templates array), and clarifies that templateName is required for subsequent calls to get_template_detail. However, it doesn't mention potential limitations like pagination 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.

  Conciseness5/5

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

  The description is perfectly concise with three sentences that each serve a distinct purpose: stating the tool's function, describing the return structure, and providing usage guidance. There is zero wasted text, and information is front-loaded appropriately.

  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's low complexity (no real parameters, no output schema, no annotations), the description is nearly complete. It explains what the tool does, what it returns, and how to use the output. The only minor gap is lack of explicit mention that this is a read-only operation, though that's reasonably inferred from the 'get' prefix and list functionality.

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

  Parameters4/5

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

  The input schema has 100% description coverage but only documents a dummy parameter. The description correctly indicates this is essentially a no-parameter tool by not mentioning any required inputs, adding value beyond the schema. It compensates for the dummy parameter's lack of real meaning by focusing on the tool's parameterless nature.

  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 with specific verbs ('获取可用的开发记录模板列表') and resource ('模板列表'). It distinguishes from its sibling tool 'get_template_detail' by explaining this tool discovers available templates while the sibling gets specific template content.

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

  Usage Guidelines5/5

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

  The description provides explicit guidance on when to use this tool ('使用此工具来发现可用的模板') and when to use the alternative ('然后使用返回的 templateName 来获取具体模板内容'). It clearly establishes the workflow relationship with the sibling tool.

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