Server Quality Checklist

Tool Scores

• search_productsA
  4.2/5.0
  Behavior4/5

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

  Annotations already provide readOnlyHint=true and destructiveHint=false, but the description adds explicit exclusions: '購入、注文、アカウント変更は行いません' (does not purchase, order, or change accounts). This adds concrete behavioral context beyond the generic hints.

  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 three short sentences, front-loaded with the core action, followed by the read-only clarification and the parameter requirement. Every sentence earns its place with no redundant or vague text.

  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 rich schema (15 parameters, all described, plus output schema) and safety annotations, the description is adequate. It covers the primary usage constraint and read-only scope, while the schema handles the rest. Slightly reduced because it doesn't summarize other constraints, but they are present in the schema.

  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%, with every parameter having a description. The tool description only repeats the query-or-jan_code requirement already present in the schema's allOf/anyOf and its overall description, adding no new semantic meaning.

  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 states 'Yahoo!ショッピングの商品を検索します' (searches Yahoo! Shopping products), which is a specific verb+resource. It also explicitly says '読み取り専用' (read-only), distinguishing it from transaction tools. No siblings exist to differentiate, but this is clear and specific.

  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 advises 'queryまたはjan_codeのいずれかを指定してください' (specify either query or jan_code), giving clear parameter guidance. It also states it does not perform purchases, orders, or account changes, implicitly defining when not to use it. No alternatives exist, but the guidance is sufficient.

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