Server Quality Checklist

Tool Scores

• read_health_dataA
  4.1/5.0
  Behavior4/5

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

  No annotations are present, so the description carries the full burden. It goes beyond the basic action by disclosing that the server is intentionally read-only by design, that data lives in a local health database, and that no write tool exists. This meaningfully informs the agent that calls are safe and non-mutating.

  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 concise sentences with no filler. The first sentence front-loads the action and the specific data types, and the second adds valuable read-only context. 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-only tool with two optional, fully documented date parameters, an output schema, and explicit read-only context, the description is complete enough for an agent to invoke it correctly. The only minor gap is not naming the sibling explicitly, but the health-domain framing makes the intended use unambiguous.

  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%, with both start_date and end_date fully documented in the input schema. The description adds no parameter-level detail, but the baseline of 3 applies because the schema already provides complete parameter semantics.

  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 specific verb ('Read') and a concrete resource ('local health database'), then enumerates the exact metrics: daily steps, sleep hours, and resting heart rate. This clearly differentiates it from the sibling read_finance_data by data domain and content.

  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?

  Usage is implied by the tool name and the described health metrics, but the description does not explicitly say when to choose this tool over read_finance_data or provide exclusion conditions. The read-only statement does address the absence of a write counterpart, but it does not fully position this tool against its sibling.

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

• read_finance_dataA
  4.3/5.0
  Behavior4/5

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

  With no annotations, the description carries the burden and does disclose a key behavioral trait: the server is intentionally read-only and there is no corresponding write tool. This tells the agent the call has no side effects, though it does not cover more detailed behavior like failure modes or permissions.

  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?

  Two tightly written sentences: the first states the action and resource, the second adds important read-only context. No filler or redundancy.

  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 three optional parameters all documented in the schema and an output schema present, the description is complete: it states the domain, the safety model, and the absence of a write counterpart. Nothing necessary for correct invocation 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 description coverage is 100%, and each parameter already has detailed semantics (format, defaults, empty-list behavior). The tool description adds no parameter information, so the baseline 3 applies.

  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 names a specific verb and resource: 'Read categorized expenses from the local finance ledger database.' The finance-ledger scope clearly distinguishes it from the sibling read_health_data.

  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?

  It gives clear context: this tool is for finance-ledger expense reads, so an agent can infer it is the right choice for finance data and not health data. It does not explicitly name read_health_data as the alternative, so it falls just 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.