Server Quality Checklist

Tool Scores

• server_infoB
  3.4/5.0
  Behavior2/5

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

  Annotations already declare readOnlyHint=true, and the description adds no extra behavioral context beyond restating the high-level purpose. No mention of potential latency, authentication, errors, or what specific statuses are returned; this is not a meaningful behavior disclosure beyond the annotation.

  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 short fragment 'Health/status of the server.' is direct and front-loaded with the key purpose, with no filler. It is a bit terse but appropriate for a zero-parameter status tool.

  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 that there are no parameters, an explicit output schema exists, and annotations signal non-mutating behavior, the description suffices for basic selection and invocation. It only lacks a little more explicit detail about what 'health/status' includes, but the schema and purpose cover the core context.

  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?

  There are no parameters, so the baseline for parameter semantics is 4. The description correctly implies a parameterless lookup and does not need to compensate for any schema deficiency.

  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 identifies the resource (server) and the kind of output (health/status), distinguishing this tool from a conversational sibling like greet. It lacks an explicit verb, but the intent is unmistakable for an info-gathering tool.

  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 need for server health/status is clear and implicitly separates it from greet, but no explicit when-to-use guidance or exclusions are provided. The description leaves the agent to infer that this tool is the correct choice only when server status is needed.

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

• greetA
  4.4/5.0
  Behavior4/5

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

  The readOnlyHint annotation already signals no side effects, but the description adds specific behavior: accepted language formats, supported language list, default-to-English when language is unset, and the exact return shape {language, greeting, message}. This goes beyond the annotations without contradicting them.

  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, front-loaded with the core purpose, and every sentence adds value: language flexibility, supported languages, name personalization, and return shape. There is no jargon or filler.

  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 two-parameter, zero-required tool with an output schema and read-only annotation, the description fully covers what an agent must know to invoke it correctly. It explains input formats, defaults, personalization, and expected output, leaving no significant gap.

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

  Parameters5/5

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

  Schema description coverage is 0%, so the description carries the full burden for the two parameters. It thoroughly explains 'language' as accepting names, alternate spellings, or ISO codes case-insensitively, enumerates allowed values, and explains the optional 'name' for personalization. This fully compensates for the empty schema descriptions.

  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 action and resource: 'Return a friendly greeting in the requested language.' It is immediately clear what the tool does and how it differs from the sibling server_info, which provides server metadata.

  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 implies when to use it by defining its purpose and parameters, but it does not explicitly say 'use this when the user wants a greeting' or contrast it with sibling server_info. Usage context is clear enough for an agent, but there is no explicit guidance about when not to use it or what alternatives exist.

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