Server Quality Checklist

Tool Scores

• dros_evaluateC
  2/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 the full burden of behavioral disclosure. It mentions 'deterministic' and 'sub-microsecond latency', which are useful behavioral traits, but it does not explain side effects, whether the tool blocks/allows execution, return values, or failure modes. The key behavior—what happens with the evaluation result—is left unspecified.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness3/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single sentence with no redundancy—it is concise in the sense of being short. However, it under-specifies the tool so severely that the brevity is more a symptom of incompleteness than effective conciseness. It is not bloated, but it doesn't earn its place as a useful summary.

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

  Completeness2/5

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

  For a tool with no output schema and no annotations, the description must carry a heavy burden. It gives only a vague functional hint and a couple of non-functional attributes, but fails to describe inputs, outputs, side effects, or evaluation semantics. The tool is not adequately contextualized for correct invocation.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters1/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 0%, and the description does not explain or even mention the parameters 'capability' or 'parameters'. There is no indication of what values 'capability' accepts or what structure 'parameters' should follow. The description adds no meaning beyond the bare schema, leaving the agent unable to construct a valid invocation.

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

  Purpose2/5

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

  The description uses vague, jargon-heavy language ('in-band execution guardrail', 'evaluating actions') without clarifying concretely what the tool does. The verb 'evaluating' and resource 'actions' are generic, and the purpose remains ambiguous—it is not obvious what action is evaluated, how, or for what decision.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  No guidance is given about when to use this tool. With no sibling tools listed, there are no alternatives to contrast against, but the description also lacks any context about the intended invocation scenario or prerequisites. The agent is left to infer usage entirely from the tool name and vague description.

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