Server Quality Checklist

Tool Scores

• search_cardsB
  3.3/5.0
  Behavior3/5

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

  Annotations already provide readOnlyHint=true (safe read operation) and openWorldHint=true (open-ended querying), so the description doesn't need to repeat these. It adds some context by specifying searchable fields (name, effect text), but doesn't disclose behavioral traits like result limits, sorting, pagination, or error handling. With annotations covering safety and scope, this is adequate but not rich in additional behavioral details.

  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, efficient sentence in Chinese that directly states the tool's function without redundancy. It's front-loaded with the core action ('通过关键字搜索游戏王卡牌') and adds necessary detail ('可以搜索卡牌名称、效果文本等'). There's zero waste, making it highly concise and well-structured for quick understanding.

  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 tool's low complexity (single parameter, no output schema), annotations provide safety and scope hints, and the description covers the basic purpose, this is minimally viable. However, it lacks details on output format (e.g., what data is returned), error cases, or integration with siblings, leaving gaps that could hinder effective use by an AI agent in more complex scenarios.

  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 has 100% description coverage, with the 'query' parameter documented as supporting card names and effect descriptions. The description adds minimal value by restating this in Chinese ('可以搜索卡牌名称、效果文本等'), but doesn't provide extra semantics like query syntax examples, character limits, or language support. Baseline 3 is appropriate since the schema does the heavy lifting.

  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: searching Yu-Gi-Oh cards by keyword across name and effect text. It uses specific verbs ('搜索' - search) and resources ('游戏王卡牌' - Yu-Gi-Oh cards). However, it doesn't explicitly distinguish from sibling tools like get_card_by_id (which retrieves by ID) or get_card_image (which fetches images), leaving some ambiguity about when to choose this over 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?

  The description provides no guidance on when to use this tool versus alternatives. It mentions what can be searched (name, effect text) but doesn't specify scenarios where this is preferred over get_card_by_id (e.g., for exact ID-based lookup) or get_card_image (e.g., for visual content). There's no mention of prerequisites, limitations, or exclusions, leaving usage context implied at best.

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

• get_card_by_idA
  3.5/5.0
  Behavior3/5

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

  Annotations already declare readOnlyHint=true (safe read operation) and openWorldHint=true (may return unknown data). The description adds the specific scope of '单张游戏王卡牌' (single Yu-Gi-Oh! card), which provides useful context beyond annotations. However, it doesn't disclose additional behavioral traits like error handling, rate limits, or response format details.

  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, efficient sentence that directly states the tool's purpose with zero wasted words. It's appropriately sized for a simple lookup tool and front-loaded with essential information.

  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 read operation with good annotations (readOnlyHint, openWorldHint) and full schema coverage, the description is minimally adequate. However, with no output schema, it doesn't explain what '详细信息' (detailed information) includes, leaving gaps about return values. The tool's low complexity keeps it from being incomplete, but it could be more comprehensive.

  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%, with the parameter 'id' fully documented in the schema as '游戏王卡牌ID，通常为八位数字' (Yu-Gi-Oh! card ID, usually an eight-digit number). The description doesn't add any parameter semantics beyond what the schema already provides, so baseline 3 is appropriate.

  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: '通过卡牌ID获取单张游戏王卡牌的详细信息' (Get detailed information of a single Yu-Gi-Oh! card by card ID). It specifies the verb '获取' (get) and resource '卡牌详细信息' (card details), but doesn't explicitly differentiate from sibling tools like 'search_cards' which likely searches by criteria rather than specific ID.

  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 (when you have a specific card ID), but doesn't explicitly state when to use this tool versus alternatives like 'search_cards' or 'get_card_image'. No guidance on prerequisites, exclusions, or comparative scenarios is provided.

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

• get_card_imageA
  3.6/5.0
  Behavior3/5

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

  Annotations already provide readOnlyHint=true and openWorldHint=true, indicating safe read-only access to potentially unknown data. The description adds context about retrieving images specifically, but doesn't disclose additional behavioral traits like image format, size, error handling, or rate limits that would be valuable beyond annotations.

  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, efficient sentence in Chinese that directly states the tool's purpose without any fluff. It's appropriately sized and front-loaded with the core functionality, earning its place clearly.

  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 (single parameter, read-only), rich annotations (readOnlyHint, openWorldHint), and 100% schema coverage, the description is reasonably complete. However, without an output schema, it doesn't explain return values (e.g., image format, error responses), leaving a minor gap for a tool that fetches binary data.

  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%, with the parameter 'id' fully documented in the schema as '游戏王卡牌ID，可以使用search_cards工具搜索'. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline for high schema coverage.

  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 verb ('获取' - get) and resource ('游戏王卡牌的图片' - Yu-Gi-Oh card image) with specific scope ('通过卡牌ID' - via card ID). It distinguishes from sibling 'get_card_by_id' by focusing on images rather than general card data, but doesn't explicitly mention 'search_cards' as a source for IDs.

  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 when needing card images specifically, and the input schema references 'search_cards' as a way to find IDs. However, it lacks explicit guidance on when to choose this tool over 'get_card_by_id' (which might also return images) or clear prerequisites beyond having a card ID.

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