Server Quality Checklist

Tool Scores

• create_replenishment_orderA
  3.9/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 full burden. It only notes that quantity must be positive, but fails to disclose behavioral traits like whether the action is irreversible, required permissions, or rate limits. The word 'create' implies mutation, but more transparency is needed.

  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?

  Two sentences, front-loaded with purpose. Efficient and no wasted words. Could potentially be slightly more concise, but it's well-structured.

  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 simple tool with three required parameters and no output schema, the description provides adequate context: purpose, usage trigger, and parameter note. Could mention response or constraints (e.g., max quantity) but overall complete.

  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 coverage is 100%, so the schema describes all parameters. The description adds the note that quantity is 'number of units to order (positive integer)', but this largely repeats schema info. No meaningful new semantic context beyond 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's purpose: 'Raise a replenishment (restock) order for a store/SKU via StoreLink.' The verb 'raise' and resource 'replenishment order' are specific, and it distinguishes from the sibling tool by implying this is the action after inventory check.

  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?

  Explicitly states when to use: 'Use after get_store_inventory_and_sales shows a meaningful demand gap.' This provides clear context and prevents misuse.

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

• get_store_inventory_and_salesA
  4/5.0
  Behavior3/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 mentions returning pre-computed fields but omits details like read-only nature, error handling, rate limits, or authentication requirements. Some transparency is present but incomplete.

  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 two sentences, front-loaded with the action, and contains no extraneous information. It efficiently communicates the tool's purpose and key return values.

  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?

  Despite lacking an output schema, the description mentions the key return fields (demand_gap, stockout_risk) which are critical for its usage. For a simple tool with two parameters, the description covers the main points, though it could include more behavioral context.

  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%, so the input schema already documents both parameters adequately. The description adds no additional parameter semantics beyond what the schema provides, meeting the baseline.

  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 verb (fetch) and resource (store/SKU inventory and sales). It explicitly distinguishes itself from the sibling tool 'create_replenishment_order' by highlighting that it combines two data points and provides pre-computed metrics for replenishment decisions.

  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 implies usage context: when you need both inventory and sales for replenishment, avoiding two calls. However, it does not explicitly state when not to use it or list alternative tools beyond the sibling.

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