Server Quality Checklist

Tool Scores

• servicenow_get_aggregateB
  3.2/5.0
  Behavior3/5

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

  Annotations already declare readOnlyHint=true, so the description carries a lower burden. The description adds that the tool supports grouping and multiple aggregation functions, but does not disclose potential limitations such as maximum output size, behavior on empty tables, or permission requirements. It adequately conveys the read-only nature but lacks depth.

  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 sentence with no fluff, achieving high conciseness. However, it could be slightly more structured (e.g., listing parameters) without adding much length. It is not overly verbose, but the brevity sacrifices some clarity.

  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?

  Given 8 parameters (1 required), no output schema, and low documentation coverage, the description is insufficient. It does not explain the return format (e.g., JSON object with aggregate values), any limits on results, or typical usage patterns. The tool's complexity demands more context.

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

  Parameters2/5

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

  Schema description coverage is only 13%, meaning most parameters lack schema descriptions. The description mentions 'count, avg/sum/min/max, optionally grouped', which maps to fields like avgFields, sumFields, groupBy, etc., but does not explain the `query` parameter or `table`. This provides some context beyond the bare schema but is insufficient overall.

  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 runs the Aggregate/Stats API on a table and lists specific operations (count, avg/sum/min/max) with optional grouping. It distinguishes itself from siblings like servicenow_get_record and servicenow_query_records, which retrieve individual records or lists rather than summaries.

  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?

  The description provides no guidance on when to use this tool over its siblings. It does not mention alternatives, prerequisites, or scenarios where aggregate stats are appropriate versus fetching records. For example, it doesn't state 'Use this when you need summary statistics rather than individual records.'

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

• servicenow_get_table_schemaB
  3.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. The description adds that inherited fields are included, which is useful behavioral context 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 description is a single concise sentence, front-loading the core purpose. It could include brief parameter hints without losing conciseness, but overall efficient.

  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 simple schema-listing tool with no output schema and no param descriptions, the description omits important details about return format and parameter behavior, leaving the agent under-informed.

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

  Parameters1/5

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

  Schema description coverage is 0%, and the description fails to explain what the 'table' and 'mandatoryOnly' parameters mean. The agent gets no help understanding parameter semantics from the description.

  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 lists fields of a table, including inherited fields, which is a specific verb+resource. It is distinct from sibling tools (get_aggregate, get_record, etc.) that deal with data or update sets.

  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 does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention prerequisites like table existence. However, the distinct purpose from sibling tools allows reasonable inference.

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

• servicenow_get_recordA
  3.7/5.0
  Behavior3/5

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

  Annotations include readOnlyHint=true, and description states 'Fetch', which is read-only. No additional behavioral details beyond annotations.

  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?

  Single sentence, no wasted words. Front-loaded with action and key constraints.

  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?

  For a simple read tool with annotations and three parameters, the description is mostly complete. Lacks guidance on fields usage and error scenarios, but sufficient for basic use.

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

  Parameters2/5

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

  Description only mentions table and sys_id, ignoring the optional 'fields' parameter. Schema provides descriptions for the two required parameters but not for fields. The description adds no extra meaning beyond the schema for the covered parameters.

  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 clearly states 'Fetch a single record by table and sys_id', which is specific verb+resource. It distinguishes from sibling tools like servicenow_query_records (query) and servicenow_get_aggregate.

  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?

  No explicit guidance on when to use vs alternatives. Implied by purpose, but lacks when-not-to-use and alternative tool names.

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

• servicenow_query_recordsA
  3.8/5.0
  Behavior4/5

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

  Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds valuable behavioral context: limit cap at 500 and return of pagination info. No contradictions.

  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 succinct sentences. First sentence states the core purpose; second provides critical usage detail (limit cap). No redundant or extraneous content. Highly efficient.

  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?

  For a tool with 6 parameters and no output schema, the description is minimal. It covers the query mechanism and a key constraint (limit 500), but omits details on pagination format, offset behavior, and return structure. Adequate but not comprehensive.

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

  Parameters2/5

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

  Schema description coverage is 50% (3 of 6 parameters have descriptions). The description does not clarify the undocumented parameters (limit, offset, displayValue). It adds no parameter-level meaning beyond what the schema provides, and fails to compensate for the gaps.

  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 clearly states the verb 'Query' and resource 'ServiceNow table', and specifies 'encoded query'. It distinguishes from sibling tools like servicenow_get_record (single record) and servicenow_get_aggregate. Includes additional detail about pagination info and limit cap.

  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?

  Implies usage for querying tables with encoded queries, but does not explicitly state when to use versus alternatives such as servicenow_get_record or servicenow_get_aggregate. No exclusion or when-not guidance is provided.

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

• servicenow_get_current_update_setA
  4.2/5.0
  Behavior3/5

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

  The readOnlyHint annotation already signals safe read-only behavior. The description adds no additional behavioral detail beyond what the annotation provides, which is adequate for a simple read operation.

  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?

  Single concise sentence that front-loads the purpose. No extraneous words. Every word is earned.

  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?

  For a tool with no parameters and no output schema, the description sufficiently explains the tool's function. It covers what the tool does and for whom, which is complete enough for an AI agent.

  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, and schema coverage is 100%. The description correctly omits parameter details. Baseline for zero parameters is 4, and no additional info is needed.

  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 verb 'Show' and resource 'current update set' for the authenticated user. It distinguishes from siblings like servicenow_get_record which operate on records, not update sets.

  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?

  No explicit when/when-not guidance, but the tool name and sibling tools make context obvious. The description implies it's for viewing the current update set, which is a specific use case separate from querying records or aggregates.

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