Server Quality Checklist

Tool Scores

• calculateC
  2.9/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 only states what the tool does, not what it returns (e.g., numeric result) or how errors like division by zero are handled. The lack of any behavioral detail beyond the operation leaves the agent guessing.

  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 a single, front-loaded sentence with no wasted words. It is appropriately concise for a simple arithmetic tool, though the brevity results in some ambiguity when considered in isolation.

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

  Completeness3/5

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

  The tool is simple, the schema completely documents parameters, but there is no output schema or annotations. The description does not disclose return format or error behavior, which is a notable gap. However, given the tool's low complexity and complete parameter schema, the incompleteness is not severe.

  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%, covering all three parameters (a, b, operation). The description adds no additional semantic meaning beyond the schema, so the baseline score of 3 applies. No enrichment or caveats are provided.

  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 'Perform basic arithmetic calculations' clearly states the tool's purpose with a specific verb and resource. It distinguishes from the sibling 'convert_temperature' because arithmetic is a general category, though it does not explicitly list supported operations. The schema's enum fills that gap.

  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 provided for when to use this tool versus alternatives. The description does not mention any exclusions, prerequisites, or when convert_temperature would be more appropriate. Usage must be inferred purely from the name and sibling context.

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

• convert_temperatureB
  3.4/5.0
  Behavior2/5

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

  No annotations provided, so the description must disclose behavior fully. It mentions two modes ('file content or direct input') but fails to clarify that the schema requires file_name, file_type, and file_content for all calls, nor how direct input actually works alongside required file parameters. Expected output and error behavior are also absent.

  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 short sentences, front-loaded with the core action and supported units. Every word earns its place, with no redundant or filler content.

  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?

  The tool has 6 parameters, no annotations, and no output schema, yet the description is minimal. It does not explain how file-based mode differs from direct input, what the result format is, or why file parameters are required. This leaves significant gaps for correct invocation.

  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 detailed param descriptions. The description adds a high-level distinction between file-based and direct input modes, but does not map parameters to modes or explain the required file parameters in that context. Thus it adds limited value beyond the 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?

  Description states 'Convert temperature units' with a specific verb and resource, and specifies supported scales (C and F). This clearly distinguishes it from the generic sibling 'calculate'.

  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: the tool is for temperature conversion when needed. However, there is no explicit guidance on when to use it versus 'calculate', no alternatives, and no exclusions or conditions.

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