Server Quality Checklist

Tool Scores

• get_checklistA
  3.8/5.0
  Behavior3/5

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

  With no annotations, the description carries the full behavioral burden. It discloses the key branching behavior (one vs. all checklists) and implies a read-only operation through 'Return'. However, it does not mention what happens when an invalid standard id/name is passed, whether results are ordered, or any other side effects or access considerations.

  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 sentence front-loads the action and resource, then explains the optional parameter behavior and the intended use case. Every clause earns its place, with no repetition or filler.

  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 tool with one optional parameter and simple semantics, the description is sufficiently complete for an agent to select and invoke it correctly. It lacks details about the return structure, but the absence of an output schema and the simplicity of a checklist retrieval make that a minor gap.

  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 description adds only marginal meaning beyond the schema: it clarifies that the id is a 'standard id/name' and that omission returns 'every checklist across the library'. This is useful context but largely reinforces what the parameter description already states.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose4/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states a specific verb ('Return'), a specific resource ('compliance checklist(s)'), and the two modes of operation: pass an id/name for one checklist or omit for all. It is distinct enough from the sibling tools (which target 'standards' rather than 'checklists'), though it doesn't explicitly name a sibling alternative.

  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 clear context for when to use the tool: as a Definition-of-Done gate before shipping, and explains the optional-id behavior. It does not, however, explicitly compare against list_standards, search_standards, or get_standard, so exclusion guidance is only implied by the different resource type.

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

• get_standardA
  3.8/5.0
  Behavior3/5

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

  With no annotations, the description carries the behavioral burden. It communicates that this is a retrieval operation returning a full standard, but it does not disclose behavior such as error handling on unknown ids, response format, or any side-effect safety guarantee. The read-only nature is implied by "Return" and "get," but not explicitly stated.

  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 behavior and identifier modes, followed by a single relevant usage note. Every sentence earns its place, and there is no redundant or filler content.

  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 single-parameter read tool with no output schema, the description covers the input aliases, the retrieval purpose, and the workflow position after search. It could add a note about what happens when no standard matches, but the core information needed to call it correctly is present.

  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 single id parameter as accepting a standard id, slug, or name. The description adds matching examples, reinforcing meaning but not significantly exceeding the schema. Baseline 3 is appropriate here.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose4/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the tool returns a full engineering standard by id, slug, or name, with concrete examples. It is specific about the resource and identifier formats. It does not explicitly contrast itself with siblings, but the target behavior is unambiguous.

  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 clear contextual guidance: "Use after search to read the complete rules and checklist." This tells the agent when the tool fits in a workflow. It does not explicitly enumerate when not to use it or name alternative tools, 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.

• search_standardsA
  4.1/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 behavioral disclosure burden. It transparently states this is a natural-language search that returns rule sections with standard, heading, and snippet, and implies a read-only operation. It doesn't cover edge cases like no matches or ranking details, but the core behavior is clearly disclosed.

  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 first sentence is tight and front-loaded with the core purpose. The second sentence is longer but earns its place by giving an explicit list of topics where the tool should be applied. No filler or redundant phrases are present, though the topic list makes it slightly longer than minimal.

  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 two-parameter search tool with no output schema, the description adequately covers the query type, return structure, and usage context. It does not mention what happens when no relevant sections are found or how relevance is ranked, but the described output shape is sufficient for an agent to invoke the tool and interpret results.

  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% and both parameters are fully documented with descriptions, defaults, constraints, and examples. The description adds no extra parameter-level meaning beyond the natural-language framing of 'query', so the schema already does the heavy lifting and a 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 states a specific verb ('Search'), resource ('standards library'), and output ('most relevant rule sections' with standard, heading, snippet). This clearly distinguishes it from sibling tools list_standards, get_standard, and get_checklist, which imply enumeration or retrieval of specific items.

  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 explicit context for when to use the tool: before answering questions about architecture, security, API, gRPC, compression, validation, messaging, UI/UX, or MCP policy. It does not explicitly mention sibling alternatives or when not to use it, but the provided topic list and 'instead of from memory' directive create a clear invocation condition.

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

• list_standardsA
  4.2/5.0
  Behavior3/5

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

  With no annotations, the description carries the burden of behavioral disclosure. It communicates that this is a listing operation and states the output fields, but does not mention pagination, ordering, or any limits; for a tool that lists 'every' standard, these details would add useful 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?

  The description is a single sentence that front-loads the action and resource, includes return fields, and adds a clear usage hint. Every part earns its place with no wasted words.

  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 parameterless list tool, the description is largely complete: it states scope, return fields, and when to use it. It could mention pagination or result volume, but the guidance is sufficient for an agent to call the tool correctly.

  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, so parameter documentation is unnecessary. The description provides more useful context about the return shape than any parameter schema could.

  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 ('List') and resource ('every engineering standard in the library'), and enumerates the returned fields. It clearly distinguishes itself from searching or fetching by positioning itself as the starting point.

  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 says 'Start here to see what rules exist before searching or fetching,' which gives clear context for when to use this tool. It does not explicitly name sibling alternatives, but the intended workflow is implied strongly enough.

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