Server Quality Checklist

Tool Scores

• get_gas_premiumA
  3.9/5.0
  Behavior3/5

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

  With no annotations, the description partially fulfills behavioral disclosure by stating the cost ($0.002 USDC via x402). However, it does not mention data freshness, return format (e.g., JSON structure), error handling, or whether the tool is idempotent. The cost transparency is valuable but incomplete.

  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 extremely concise, consisting of two short sentences that front-load the core action ('Get full 9-chain EVM gas comparison') and immediately provide supporting details (chains, cost). Every word adds value.

  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 simplicity of the tool (no parameters, no output schema), the description covers the core inputs and output concept. However, it lacks details on the return format (e.g., data structure, units) and does not describe how this tool relates to siblings, leaving some ambiguity for agent selection.

  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?

  Since the input schema has zero parameters (schema coverage 100%), the description adds meaningful context not present in the schema, specifically the cost and payment method. This goes beyond the baseline of 3.

  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 provides a 'full 9-chain EVM gas comparison' and lists all 9 chains, making the purpose explicit and distinguishing it from sibling tools like get_gas_basic (which likely covers fewer chains).

  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 usage when needing a comparison across all 9 chains, but does not explicitly state when to prefer this over siblings (e.g., get_cheapest_chain or get_gas_demo) or mention exclusion criteria. The cost mention could be a guideline but is not framed as a usage condition.

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

• get_cheapest_chainA
  4.1/5.0
  Behavior3/5

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

  Without annotations, the description mentions rate limiting but lacks details on data freshness, authentication needs, or other behavioral traits.

  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 concise, front-loaded sentences with zero waste.

  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 parameterless tool with no output schema, the description fully covers purpose and return format.

  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?

  No parameters exist, so description need not add param info; it mentions return details which provides minimal value.

  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 'Get' and the resource 'cheapest EVM chain recommendation', and distinguishes from sibling gas tools.

  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 usage for quick cost-saving query but provides no explicit guidance on when to use this vs sibling tools or alternatives.

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

• get_gas_demoA
  4.1/5.0
  Behavior3/5

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

  With no annotations, the description carries full burden. It discloses rate limiting, chain selection, and the free nature, but omits details on output format, error handling, or read-only behavior. This is adequate for a simple demo but lacks full 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 extremely concise, using two sentences that efficiently cover function and usage context with no wasted words.

  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 simplicity (no params, no output schema), the description covers core aspects but misses return format and error behavior. Partial completeness leaves gaps for an agent to infer.

  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 no parameters, and schema coverage is trivially 100%. Per the rubric, zero parameters default to baseline 4, as the description adds no parameter-specific meaning.

  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 action (get), resource (gas prices), and scope (4 specific EVM chains). It also distinguishes from siblings by noting it's free and rate-limited for a quick overview, effectively differentiating from paid or more extensive tools.

  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 explicitly advises using this tool for a quick overview without payment, providing clear context. However, it does not mention when to avoid it or suggest alternatives, so no exclusions are provided.

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

• get_gas_basicA
  4.2/5.0
  Behavior4/5

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

  Discloses cost ($0.001 USDC via x402 on Base), which is a critical behavioral trait. Without annotations, the description carries full burden; it provides this transparency but does not mention rate limits, side effects, or error behavior. Generally sufficient for a simple read-oriented tool.

  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?

  Extremely concise: two sentences cover purpose, included chains, and cost. No redundant information. Every sentence adds value, and the key action is front-loaded. For such a simple tool, this is ideal.

  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?

  Describes purpose, chains, and cost completely given no parameters and no output schema. However, it lacks details on output format (e.g., JSON vs text) and how savings calculation works. For a basic tool, this is mostly sufficient but could be slightly more explicit.

  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?

  No parameters are defined, so schema coverage is trivially 100%. Description adds context about the tool's function but cannot add parameter-level semantics. With 0 parameters, baseline is 4, and the description appropriately describes the overall behavior without needing to compensate for parameter details.

  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?

  Clearly states the tool retrieves a 4-chain EVM gas comparison with cheapest chain recommendation and savings calculation. Lists specific chains (Ethereum, Base, Arbitrum, Optimism) and cost, making purpose unambiguous. The verb 'Get' and resource 'gas comparison' are specific and distinguish from sibling tools like 'get_cheapest_chain' which likely only returns one chain.

  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 this tool versus siblings. While names imply differentiation ('basic' vs 'demo'/'cheapest_chain'/'premium'), the description does not state usage context or exclusions. It implicitly suggests this is the standard comparison tool but lacks explicit alternatives guidance.

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