Server Quality Checklist

Tool Scores

• get_methodologyA
  3.8/5.0
  Behavior3/5

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

  No annotations exist, so the description carries the full burden. It discloses the core behavior (summarize and provide a link), but omits details such as the output format, whether the summary is static or dynamic, and any access prerequisites. Adequate but not enriched.

  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, front-loaded sentence conveys the purpose and key output elements without superfluous words. Every word earns its place.

  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?

  Given the simple, parameterless nature and lack of output schema, the description adequately explains the tool's purpose and outputs (summary and link). It could specify the link format or include a note about the summary's granularity, but this is a minor gap.

  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, and the schema is an empty object, making parameter semantics irrelevant. Per rubric, a zero-parameter tool earns a baseline of 4.

  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 uses the specific verb 'summarize' and identifies the exact resource (Phi Score with 5 clinical pillars and weights). It clearly distinguishes itself from sibling tools that list or analyze biomarkers.

  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 explicit when-to-use or alternative guidance is provided. The description only states what the tool does, leaving the agent to infer when it should be selected over siblings; this falls under 'no guidance'.

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

• analyze_biomarkersA
  4.2/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 full burden of behavioral disclosure. It clearly states the endpoint is stateless and does not store inputs, which is a key safety trait. It also specifies the output format (3-tier recommendations). This goes beyond basic disclosure, though it does not cover every possible side-effect or require permissions. For an analysis tool, this is strong 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 compact and front-loaded with the core purpose. Each sentence adds value: the action, the output, the data constraints, and the statelessness. There is no filler or redundancy. Despite being slightly longer than typical, it is appropriately detailed given the safety-critical data-handling instructions.

  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?

  The description covers the main purpose, output, and important data-handling behavior. It does not mention that users should consult list_supported_biomarkers to ensure valid biomarker names, nor does it explain how age or biologicalSex affect recommendations. Given the moderate complexity (nested object, 5 params) and the absence of an output schema, the description is mostly complete but has notable gaps in prerequisites and parameter influence.

  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 60%, so the description should compensate for the undocumented parameters (age, biologicalSex). The description only refers to 'biomarker panel' and the output tiers, adding little detail about how age, biologicalSex, conditionFocus, or include_partner_options affect results. The schema itself describes biomarkers, conditionFocus, and include_partner_options, but age and biologicalSex remain unexplained in both schema and description, leaving a gap.

  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 the tool's function: it analyzes a SYNTHETIC biomarker panel using the PRISM engine and returns 3-tier recommendations. This distinguishes it from siblings list_supported_biomarkers (which lists biomarkers) and get_methodology (which explains methodology). The verb 'analyze' plus the resource 'biomarker panel' makes the purpose unmistakable.

  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 strong context for when to use the tool: it is intended for research/education with synthetic or de-identified data, explicitly forbids PHI, and notes the stateless nature. However, it does not explicitly contrast this tool with its siblings or state conditions like 'use when you need recommendations' versus 'use list_supported_biomarkers when checking available biomarkers'. The usage is implied rather than fully explicit.

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

• list_supported_biomarkersA
  4.5/5.0
  Behavior4/5

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

  With no annotations provided, the description carries the full burden. It discloses that the tool returns reference data only, not patient data, and reveals the structure (grouped by clinical pillar). This is sufficient for a simple list operation, though it does not detail any edge cases or side effects, which are unlikely here.

  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 action and resource, and each sentence adds value: the first explains what is listed, the second clarifies the scope and data type. No wasted words.

  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 zero parameters and no output schema, the description is complete: it tells the user what the tool does, what information is returned, and what the result is grouped by. The distinction from patient-data tools is also covered, making it sufficient for a low-complexity tool.

  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 the baseline is 4. The description adds meaning by explaining what the list contains (biomarkers, units, reference ranges) and how it is organized, which is more than necessary for an empty schema.

  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 ('biomarkers PRISM scores'), with added detail on units, reference ranges, and grouping by clinical pillar. It also distinguishes itself from siblings by clarifying 'Reference data only — no patient data', which separates it from tools like analyze_biomarkers.

  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 phrase 'Reference data only — no patient data' provides clear context on when to use this tool (for reference lookups, not patient-specific queries). While it does not explicitly name alternatives, the sibling context and this exclusion make the intended use clear.

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