Server Quality Checklist

Tool Scores

• check_packageA
  4.1/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 disclosure burden and handles it well: it states that the call returns existence and flags specific risk patterns (slopsquatting, install-time scripts, deprecation, abandonment), which implies a read-only verification behavior. It does not disclose network behavior or error handling for invalid package names, but those are minor gaps for a verification tool.

  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?

  The description is three sentences, front-loading the purpose with an imperative verb and the resource immediately. The second sentence's list of risk flags is compact and useful, and the parenthetical on slopsquatting justifies the niche term. Nothing is redundant, though the list of flags makes it slightly long.

  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 one-parameter tool with no output schema and no annotations, the description covers what the tool does, what it returns, and when to call it. The absence of an output schema makes the described return values particularly valuable. Edge-case behavior (e.g., result shape for a nonexistent package or network errors) is not addressed, but this is a minor omission for a single-package check.

  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%: the single parameter 'name' is already documented with format and examples ('express' or '@scope/pkg'). The description does not add meaning beyond what the schema provides, so the baseline score of 3 is appropriate. It correctly reinforces the singular scope, but adds no new parameter semantics.

  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 states a specific verb ('Verify'), a specific resource ('a single npm package'), and the context ('before installing, importing, or recommending it'). It implicitly distinguishes from its plural sibling check_packages by emphasizing 'single', and it enumerates exactly what the check returns: existence, slopsquatting, install-time scripts, deprecation, and abandonment. This leaves no ambiguity about what the tool does.

  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 gives an explicit trigger: 'Call this whenever you are about to introduce a dependency you have not verified in this session.' This is clear when-to-use guidance. However, it does not explicitly state when not to use it or name the alternative (e.g., a batch-check sibling), though the singular/plural naming and the verb make the boundary reasonably obvious.

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

• check_dependenciesA
  4.2/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 behavioral disclosure burden. It adds meaningful behavior by stating that results are sorted worst-first, ensuring hallucinated or dangerous packages surface at the top. It does not describe the response format or side effects, but 'verify' strongly implies a non-mutating operation.

  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 compact and front-loaded: it states the core action first, then practical use cases, then the key behavioral nuance about sorting. Every sentence earns its place with 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 one-parameter tool with no output schema, the description provides enough context to invoke it correctly: when to use it, what it accepts, and what results look like. It could be more complete by naming check_package as the single-package alternative or describing the result payload, but these are minor gaps.

  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 already documents the 'names' parameter well. The description reinforces the batch aspect and ties it to dependency-list checks, but it does not add substantially new parameter-level detail beyond what the schema provides.

  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 ('Verify') with a clear resource ('many npm packages at once'), which immediately conveys the tool's batch nature. This distinguishes it from the sibling check_package, which presumably handles a single package.

  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 explicitly states when to use the tool: before writing a package.json, running an install command, or handing a dependency list to a user. It does not explicitly mention the alternative for single-package checks, but the batch-focused phrasing provides clear contextual guidance.

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