Server Quality Checklist

Tool Scores

• TIME CALCULATORB
  3.3/5.0
  Behavior2/5

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

  With no annotations provided, the description carries full burden for behavioral disclosure. While it mentions the types of operations, it doesn't disclose important behavioral traits like whether operations are read-only or mutating, error handling for invalid inputs, performance characteristics, or what the return values look like. For a complex tool with 12 parameters, this is a significant gap in behavioral transparency.

  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 appropriately sized with two sentences that efficiently cover purpose and usage. The first sentence establishes the scope of operations, and the second provides specific use cases. There's no wasted text, and information is front-loaded, though it could be slightly more structured by grouping related operations.

  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?

  For a complex tool with 12 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't address what the tool returns, how errors are handled, performance considerations, or provide guidance on parameter combinations for different operations. The schema covers parameter definitions well, but the description fails to provide the contextual understanding needed for effective tool use.

  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%, so the schema already documents all parameters thoroughly. The description adds no specific parameter semantics beyond what's in the schema - it doesn't explain how parameters interact, which parameters are required for which operations, or provide additional context about parameter usage. Baseline 3 is appropriate when the schema does all the parameter documentation work.

  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 clearly states the tool performs 'time arithmetic operations' and lists specific functions like duration calculations, date math, and sorting. It distinguishes from the sibling 'GET TIME' by emphasizing calculations rather than retrieval, though it doesn't explicitly contrast them. The verb+resource combination is specific but could be more precise about the computational nature.

  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 clear usage contexts with 'Use for adding/subtracting time periods, calculating differences between dates, analyzing time-based datasets, or sorting arrays of timestamps.' This gives explicit when-to-use guidance for different scenarios. However, it doesn't mention when NOT to use it or explicitly compare with the sibling 'GET TIME' tool.

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

• GET TIMEA
  3.9/5.0
  Behavior3/5

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

  With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the default behavior and some operational details (multiple timezones/formats handling), but doesn't cover important aspects like error handling, rate limits, authentication requirements, or what the output structure looks like. The description adds some value but leaves significant behavioral gaps.

  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 efficiently structured with three sentences that each serve a distinct purpose: stating the core functionality, describing default behavior, and explaining array parameter usage. There's no wasted verbiage and information is front-loaded appropriately.

  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?

  Given the tool's moderate complexity (5 parameters, timezone/formats logic) and lack of both annotations and output schema, the description is incomplete. While it covers basic usage, it doesn't explain the output format, error conditions, or provide examples of what the tool returns. The description should do more to compensate for the missing structured information.

  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?

  The schema description coverage is 100%, so the schema already documents all 5 parameters thoroughly. The description adds minimal value beyond what's in the schema - it mentions the timezones and formats arrays but doesn't provide additional semantic context. This meets the baseline expectation when schema coverage is complete.

  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 purpose with specific verbs ('get current time' and 'convert times across timezones') and resources (time with formatting). It distinguishes from the sibling 'TIME CALCULATOR' by focusing on retrieval/conversion rather than calculation operations.

  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 clear context for when to use the tool ('Defaults to current time in system timezone when no parameters provided') and mentions usage patterns ('Use timezones array to get multiple zones, formats array for multiple output formats'). However, it doesn't explicitly state when NOT to use it or mention the sibling tool as an alternative for calculation tasks.

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