Server Quality Checklist

Tool Scores

• get_dmr_valuesA
  4.8/5.0
  Behavior5/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 thoroughly explains key behaviors: the 'windowing trap' with date ranges, handling of zero results, interpretation of null dmrValue with nodiFlag, parameter matching, and result truncation. All behavioral traits are 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 description is well-structured with clear paragraphs and warnings. It is somewhat lengthy but each section adds value with no redundancy. Could be slightly more concise, but overall effective.

  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?

  Given the complexity (6 parameters, no output schema, no annotations, no siblings), the description is remarkably complete. It covers not only the primary function but edge cases (ambiguous names, zero results, null dmrValue), alternative tools, and behavioral nuances. No gaps identified.

  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?

  Schema description coverage is high (83%), but the description adds significant meaning beyond the schema: the windowing trap, the interaction between startDate/endDate, the substring matching behavior for parameter, and the meaning of nodiFlag. It adds value, though the schema already documents basics.

  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 it gets measured DMR values, not limits, and explicitly distinguishes from get_permit_limits. The verb 'get' and resource 'DMR values' are specific, and the distinction from the sibling is clear.

  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?

  The description provides explicit when-to-use (getting actual effluent values) and when-not-to-use (for limits, use get_permit_limits). It also gives detailed guidance on facility identification (prefer npdesId, name resolution with fallback), date range usage, filtering, and result limits.

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