Server Quality Checklist

Tool Scores

• package_apiA
  4/5.0
  Behavior4/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 discloses that the API is extracted from published TypeScript declarations (.d.ts), a key behavioral constraint, and reveals the output structure ('Grouped by kind, with one-line signatures'). Edge cases like missing .d.ts files aren't covered, but for a read-only introspection tool this is reasonably transparent.

  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 and front-loaded with the core purpose, with each sentence contributing what, when, and why. There is minor redundancy ('antidote to inventing APIs' restates the previous sentence), but overall it's efficient.

  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?

  With no output schema, the description gives a partial return shape ('Grouped by kind, with one-line signatures') but doesn't elaborate on the exact structure or error behavior. It covers the main use case well but lacks sufficient detail about limitations, given the tool's complexity.

  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 already provides 100% description coverage for all three parameters (package, version, entry), so the baseline is 3. The description echoes the version concept but adds no additional semantics beyond what the schema documents.

  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 'Get' with a precise resource ('REAL exported API' of an npm package at a specific version) and explicitly enumerates what's included (functions, classes, constants, interfaces, types). It distinguishes itself from sibling tools by claiming to be the authoritative source ('antidote to inventing APIs: if it isn't in this list, the package doesn't export it').

  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 provides an explicit when-to-use: 'Reach for this WHENEVER you're about to call into a library and aren't 100% certain a function/option exists with that exact name and signature.' This is clear context, though it does not name sibling tools or exclusions, so it stops short of a 5.

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

• list_type_filesA
  4.2/5.0
  Behavior3/5

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

  No annotations are provided, so the description carries the transparency burden. It clearly implies a read-only listing operation, but does not explicitly state the return format, network behavior, or any side effects. For a simple list tool, this is adequate but not rich in behavioral detail.

  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 core action and then usage conditions. Every word earns its place; no fluff or 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 2-parameter tool with no output schema, the description covers purpose and usage scenarios effectively. It does not describe the return value, but for a listing operation that is self-evident; overall complete enough for an agent to invoke correctly.

  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% (both package and version are described). The description adds context by combining package@version in the purpose, but does not add significant meaning beyond the schema. Baseline 3 is appropriate.

  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: 'List every TypeScript declaration (.d.ts) file shipped in an npm package@version.' This specifies the verb (list), resource (declaration files), and scope (package@version), distinguishing it from sibling tools like package_api and package_types.

  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?

  Explicit usage conditions are given: 'Use when package_api can't find the entry, when a package splits its types across many files, or to locate the declaration for one submodule/export.' This provides when-to-use guidance and names an alternative, making sibling differentiation clear.

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

• package_typesA
  4.7/5.0
  Behavior4/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 clearly implies a read-only operation ('Return the raw .d.ts declaration text') and explains the default and override behavior. It lacks an explicit statement about non-destructiveness, but the framing is sufficient. It does not cover edge cases like missing packages, but that's not required for basic transparency.

  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?

  Three sentences, front-loaded with the core purpose. The first sentence states what it does, the second explains when to use it, and the third provides a practical default and override. No redundant or filler content—every sentence earns its place.

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

  Completeness5/5

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

  For a simple read tool, the description covers the key aspects: what it returns, when to prefer it, and how to specify a particular file. Combined with the fully-documented schema and absence of an output schema (raw text), the description provides adequate context for selecting and using the tool. It even references the sibling `list_type_files` to complete the usage flow.

  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 already covers 100% of parameters, so the baseline is 3. The description adds value by linking `file` to `list_type_files`, clarifying the `package@version` syntax, and noting the default types entry. This goes beyond mere schema repetition, earning a 4.

  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 opens with a clear and specific verb phrase: 'Return the raw .d.ts declaration text for an npm package@version'. It explicitly identifies the resource (TypeScript declaration files) and distinguishes itself from siblings by mentioning 'ground-truth type definitions' and 'a summary can't capture', which sets it apart from package_api.

  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?

  Usage guidance is explicit: 'Use when you need exact signatures, generic parameters, overloads, or option-object shapes that a summary can't capture'. It also clarifies when to use the `file` parameter ('from list_type_files') and the default behavior, effectively directing the agent to the right alternative.

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