Server Quality Checklist

Tool Scores

• redact_suggestA
  3.7/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 burden of behavioral disclosure. It does state the core behavior—detecting PHI-shaped values and returning a redacted version—but it does not mention whether detection is heuristic, what kinds of PHI patterns are covered, or any limitations. It is adequate for a simple transformation tool but not richly transparent.

  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, front-loaded sentence with no waste. It states the input context, the detection behavior, and the output in a compact structure that is easy to parse.

  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 tool with no output schema, the description covers the essential context: what input is expected and what output is returned. It could add more detail about the redaction format or heuristic nature of PHI detection, but the definition is largely sufficient for correct invocation.

  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 documents the text parameter at 100% coverage, so the baseline is 3. The description adds value by giving concrete examples of acceptable input types—log line, prompt, error message—which helps the agent understand the intended scope beyond the schema's generic 'Raw text that may contain PHI'.

  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 action ('detect PHI-shaped values and return a redacted version') applied to a defined resource ('raw text snippet'). It distinguishes itself from the sibling scan_code by focusing on text snippets like logs and prompts rather than code, though it does not explicitly name the alternative.

  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 provides implied usage context: use this tool for raw text that may contain PHI-shaped values. However, it does not explicitly state when not to use it or how it compares to scan_code, leaving the routing decision partially to inference.

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

• scan_codeA
  3.8/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 full burden of behavioral disclosure. It clearly conveys a read-oriented scan behavior and the matching criteria, but it does not state whether the tool returns findings, modifies files, or has other side effects, leaving some behavior implicit.

  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, well-structured sentence that front-loads the action and then narrows the scope with specific identifiers and sinks. Every clause contributes information, with no filler 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 one-parameter tool with no output schema and no annotations, the description provides enough context for an agent to invoke it correctly: what to scan, what to look for, and when to run it. It could be improved by stating the result format or confirming it is non-mutating, but nothing essential is missing.

  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%, and the only parameter 'path' is already described as an absolute path to a directory or repo. The description adds contextual flavor like 'local' and 'source files,' but it does not add meaning beyond what the schema already provides.

  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 uses a specific verb ('Scan') and resource ('local directory of source files'), and precisely defines what it detects: sensitive identifiers flowing into risky sinks. It is clearly distinguishable from the sibling redact_suggest by its purpose, though it never explicitly names or contrasts that sibling.

  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 clear temporal and contextual guidance: run this before code ships, on local source directories, to catch sensitive data going into LLM calls, logging, or analytics. It does not explicitly name alternatives or exclusions, so it falls short of full routing guidance.

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