Server Quality Checklist

Tool Scores

• get_blockB
  3.1/5.0
  Behavior2/5

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

  With no annotations, the description carries full burden. It implies a read-only operation via 'Get' but does not disclose network default behavior, error handling for invalid identifiers, or whether the returned information includes transactions. The description adds minimal behavioral context beyond the basic 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?

  The description is a single sentence with no unnecessary words. It is concise and front-loads the core purpose effectively.

  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 simple read tool with two parameters, the description is minimally adequate. It tells the user what the tool does and how to specify a block, but without an output schema, it does not describe the returned block information structure or fields. It also does not mention the network parameter even though it exists in the schema.

  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 coverage is 100%, so the baseline is 3. The description adds no extra meaning beyond the schema; it simply repeats 'number or hash' already present in the blockIdentifier description. The network parameter is only documented in the schema, and the description does not clarify usage.

  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 verb 'Get' and the resource 'block information', and specifies the identifier types (number or hash), which distinguishes it from sibling tools that handle balances, transactions, or network info. However, it does not explicitly differentiate from alternatives or elaborate on what information is returned.

  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 on when to use this tool versus siblings like get_transaction or get_network_info. There are no exclusions, prerequisites, or context about suitable use cases.

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

• get_network_infoB
  3.1/5.0
  Behavior2/5

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

  With no annotations, the description carries the full burden of behavioral disclosure. It implies a read-only operation through 'Get' but does not disclose return format, output contents, or any limitations. Minimal behavioral detail is provided.

  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 a single, succinct sentence with no verbosity or redundancy. It is front-loaded with the action and resource, maximizing clarity and efficiency.

  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 simple tool with full schema coverage, the description is adequate but leaves gaps: no output schema exists, and the description does not specify what 'statistics' are included. It is minimally complete but could benefit from clarifying the expected return data.

  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 input schema fully documents the single optional 'network' parameter with enum values, a default, and a description, achieving 100% schema description coverage. The tool description adds no further parameter context, so the baseline score of 3 is appropriate.

  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 a specific verb and resource: 'Get 0G network information and statistics.' It distinguishes itself from siblings which focus on balances, transactions, blocks, or gas. However, the nature of 'statistics' remains somewhat vague.

  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 versus alternatives. It mentions no prerequisites, exclusions, or conditions under which sibling tools would be preferred.

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

• estimate_gasB
  3.4/5.0
  Behavior2/5

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

  No annotations are present, so the description must convey behavioral traits. It states the tool 'estimates' gas, which strongly implies it does not broadcast the transaction, but it does not explicitly confirm the read-only nature or mention that the estimate is not an execution. The description also omits potential side effects, error conditions, or how the network parameter influences the estimate, leaving key safety aspects undisclosed.

  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 a single, front-loaded sentence that directly states the purpose without any filler or repetition. Every word contributes to the meaning, and it is appropriately sized for a tool with a self-explanatory name and well-documented schema.

  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?

  With no output schema, the description should indicate what the estimate returns (e.g., gas limit or gas price) and how parameters affect the result. It provides none of this, leaving the agent to guess the return format, range, or potential errors. Given the tool's complexity (four parameters, estimation logic), the description is insufficient for reliable 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?

  Since the schema provides descriptions for all four parameters (to, data, value, network), the baseline is 3. The description adds no extra meaning beyond the schema, such as clarifying that value is in wei or that network defaults to testnet. The tool description does not need to repeat schema details, but it also offers no additional parameter context.

  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 identifies the tool's function with a specific verb ('Estimate') and resource ('gas for a transaction'), distinguishing it from sibling tools like get_balance and get_transaction. The phrase 'on 0G network' adds necessary context, though it is somewhat redundant given the tool name. Overall, it is immediately obvious what this tool does and how it differs from its siblings.

  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 preparing or analyzing a transaction, but it does not explicitly state when to use this tool versus alternatives, nor does it mention prerequisites such as valid recipient address or network selection. There is no guidance on exclusions or complementary tools, so the agent must infer the intended context from the name and schema.

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

• get_transactionA
  3.5/5.0
  Behavior2/5

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

  No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states 'Get transaction details' which implies a read-only operation, but it does not mention what happens if the hash is invalid, whether authentication is needed, rate limits, or any side effects. This is a significant gap given no annotation support.

  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 a single, front-loaded sentence with no wasted words. It efficiently delivers the core purpose and resource without any redundant or filler content.

  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 low-complexity tool with two parameters and no output schema, the description adequately identifies the operation and target, but it does not elaborate on the return format, error behavior, or network semantics beyond what the schema already lists. It is minimally complete but lacks additional context that would help an agent anticipate outcomes.

  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 both parameters (txHash and network) already well-described in the schema. The tool description adds no additional parameter semantics beyond what the schema provides, so the baseline of 3 is appropriate.

  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 uses a specific verb 'Get' with the resource 'transaction details' and clearly scopes to 'by hash on 0G network'. This clearly differentiates it from sibling tools like get_balance, get_block, and get_network_info, which target different data.

  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 a transaction hash is available, but it does not explicitly state when to use this tool versus alternatives like get_block or get_balance. No exclusions or alternative tool references are provided, though the context is fairly clear.

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

• get_balanceA
  3.8/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 burden of behavioral disclosure. It clarifies the tool performs a read operation ('Get'), but does not mention any potential side effects, network-specific behavior, or error handling. The schema covers the network default, so the description adds minimal transparency beyond the obvious.

  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 a single concise sentence that gets straight to the point. Every word earns its place, and it is front-loaded with the verb and resource.

  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 balance lookup, the description covers the core function. The schema handles parameter semantics, and no output schema exists to elaborate on return values. Given the tool's low complexity, the description is sufficiently complete, though it could have mentioned the network default explicitly.

  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 both parameters ('address' and 'network') already described in the schema. The description adds no parameter details, so the baseline score of 3 applies.

  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 uses a specific verb ('Get') and resource ('balance of an address'), and adds the network context ('on 0G network'). This clearly distinguishes the tool from its siblings (get_transaction, get_block, get_network_info, estimate_gas).

  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 the tool is used to check an address balance, but it does not explicitly state when to use it versus alternatives or mention any prerequisites. There is no 'use this for X, not Y' guidance, so usage is merely implied from the clear purpose.

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