Server Quality Checklist

Tool Scores

• add_productC
  2.7/5.0
  Behavior2/5

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

  With no annotations, the description carries the full burden of disclosing behavioral traits. It only states the action and target; it does not mention required fields, validation behavior, duplicate handling, defaults, side effects, or return values. This is minimal behavioral disclosure.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness3/5

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

  The description is a single, front-loaded sentence with no fluff, but it is under-specified for a tool with 9 parameters. It is concise structurally yet lacks the detail needed to be considered well-rounded.

  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 9 parameters, low schema coverage, no output schema, and no annotations, one sentence is insufficient. The description does not address required inputs, defaults, uniqueness, or what happens after the product is added, leaving significant gaps for safe invocation.

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

  Parameters1/5

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

  Schema description coverage is only 22%, so the description must compensate by explaining parameter meaning. It does not mention id, name, price, sku, stock, status, category, description, or manufacturer, leaving most parameters effectively undocumented from the agent's perspective.

  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 uses a specific verb ('Add'), identifies the resource ('a product'), and names the target context ('Excel catalog'). This clearly distinguishes it from sibling tools like list_products, search_products, update_product, and delete_product.

  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?

  No guidance is provided about when to choose this tool over alternatives, prerequisites, or uniqueness constraints. The verb 'Add' implies the basic use case, but the description offers no explicit when-to-use or when-not-to-use context.

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

• update_productB
  3.2/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 only says 'Update a product' without disclosing whether this is a partial update (only provided fields) or a full replacement, what happens to unmentioned fields, or what occurs if the product is not found. It also omits any side effects, permissions, or idempotency information.

  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, concise sentence that conveys the essential purpose without unnecessary words. It is appropriately sized for a simple tool and front-loads the core action.

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

  Completeness1/5

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

  For a tool with 10 parameters, no annotations, and no output schema, this description is critically incomplete. It does not mention return values, error handling, update semantics (partial vs full), or any other operational detail needed for safe usage. The agent would have to rely on the schema alone, which is insufficient given the tool's complexity.

  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 coverage is low (30%) with descriptions only on id, name, and identifier. The description adds meaning to the required identifier parameter ('current ID or exact name') but provides no clarification for the other seven parameters (price, stock, status, etc.), which lack schema descriptions. It does not compensate for the missing schema coverage.

  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 action ('Update a product') and specifies the selection mechanism ('by its current ID or exact name'), which also differentiates it from sibling tools like add_product (create) and delete_product (delete). It is a specific verb+resource description.

  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 you need to modify an existing product) by mentioning 'current ID or exact name,' but it does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or prerequisites. There is no guidance about using search first or the need for an existing product.

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

• delete_productA
  3.5/5.0
  Behavior2/5

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

  Annotations are absent, so the description must fully disclose behavior. It only says 'Delete a product' and provides no detail about irreversibility, permissions, error cases when no product is found, cascading effects, or return value. This is thin coverage for a destructive tool.

  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 one compact, front-loaded sentence. It communicates the operation, target, and parameter semantics with no wasted words or filler.

  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?

  This is a simple one-parameter destructive tool with 100% schema coverage, so the description is minimally adequate. However, no annotations or output schema are present, and the description omits outcome and failure behavior, making it not fully self-contained for an AI agent.

  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 already documents the only parameter as 'Product ID or exact name', and the description essentially restates that fact. No additional semantic guidance is provided, such as whether name matching is case-sensitive, what takes precedence when the value could be both an ID and a name, or what happens with duplicate names.

  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 commands a clear, specific operation: 'Delete a product', and identifies how the product is selected ('by ID or exact name'). This clearly distinguishes it from the CRUD sibling tools such as add_product, update_product, and list_products.

  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 intent is implicit: use this when you need to delete an existing product. However, the description does not explicitly state prerequisites, when not to use it, or how it compares with alternative operations such as update_product or search_products.

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

• list_productsA
  3.5/5.0
  Behavior2/5

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

  With no annotations available, the description carries the full behavioral disclosure burden. It merely states the action and resource, but does not reveal return format, pagination behavior, or whether it is strictly read-only, leaving the agent to infer safety and data shape.

  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 exactly one sentence, front-loaded with the action verb, and contains no extraneous information. Every word earns its place.

  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 zero-parameter listing tool, the description roughly specifies what is listed and the broader context ('the Excel catalog'). However, with no output schema and no mention of returned fields or record shape, the description is barely adequate for fully setting expectations about the tool's result.

  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 tool has zero parameters and schema description coverage is 100%, so the schema already carries all parameter information. The description adds no parameter-specific value, which is acceptable given the baseline of 4 for no-parameter tools.

  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 uses the specific verb 'List' with the resource 'every product in the Excel catalog,' clearly defining an exhaustive listing operation. It differentiates from sibling search_products by emphasizing completeness ('every product') without any filtering.

  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?

  No guidance is provided about when to use this tool versus search_products, add_product, update_product, or delete_product. The description gives no context for when listing all products is appropriate or when an alternative should be chosen.

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

• search_productsA
  3.8/5.0
  Behavior2/5

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

  No annotations are provided, and the description does not disclose behavioral details such as result format, filtering behavior (exact vs. partial match), pagination, or case sensitivity. It only repeats the searchable fields, which overlaps with parameter semantics.

  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?

  A single, front-loaded sentence that uses minimal words to convey the tool's purpose and parameter scope. No redundancy.

  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 simple tool with one parameter and no output schema, the description adequately covers purpose and parameter meaning. It could mention return behavior, but the tool is straightforward enough that the current description is mostly sufficient.

  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 schema only describes 'query' as 'Text to search for', but the tool description enriches it by listing the fields that can be matched (ID, name, description, etc.), providing meaningful context beyond the schema.

  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 searches products and enumerates specific fields (ID, name, description, category, SKU, manufacturer, or status), distinguishing it from sibling tools like list_products which lists all, and add/update/delete which are mutations.

  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 for finding products by specific attributes but does not explicitly state when to prefer this over list_products or provide exclusions. No alternative tools are mentioned.

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