Server Quality Checklist

Tool Scores

• ab_deploy_token_erc20A
  3.9/5.0
  Behavior4/5

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

  The description adds valuable behavioral context beyond the destructiveHint annotation. It discloses the deployment method ('proven zksync-ethers deployment method via subprocess'), return value ('Returns the deployed contract address'), and security prerequisites ('deployer wallet must have enough funds'). While annotations cover the destructive nature, the description provides implementation details and constraints that help the agent understand the tool's behavior.

  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 well-structured with clear sections (PARAMETERS, FLOW, SECURITY/LIMITATIONS) and front-loads the core purpose. While somewhat verbose, each section serves a purpose. The structure helps with readability, though some content duplication with the schema reduces efficiency.

  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 destructive deployment tool with no output schema, the description provides good contextual completeness. It covers the deployment method, return value, and security prerequisites. The main gap is the undocumented debug parameter, but overall it gives the agent sufficient understanding of what the tool does and what to expect.

  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?

  With 100% schema description coverage, the schema already documents all parameters thoroughly. The description's PARAMETERS section repeats information already in the schema (name, symbol, initialSupply definitions) without adding meaningful semantic context. The debug parameter isn't mentioned at all in the description. Baseline 3 is appropriate when schema does the heavy lifting.

  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 specific action ('Deploy an ERC-20 BasicToken') and target resource ('to the Abstract network'), distinguishing it from sibling tools like balance checking or transfers. It provides a complete verb+resource+scope statement that leaves no ambiguity about the tool's function.

  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 context through the SECURITY/LIMITATIONS section mentioning deployer wallet requirements, but doesn't explicitly state when to use this tool versus alternatives. No sibling tool comparisons or explicit when/when-not guidance is provided, leaving usage context somewhat implied rather than clearly defined.

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

• ab_agw_create_walletA
  4.2/5.0
  Behavior4/5

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

  Annotations provide destructiveHint=true, indicating this is a write operation. The description adds valuable context beyond annotations: it specifies that the tool wraps an external helper ('@abstract-foundation/agw-client’s deployAccount'), describes the return values (address and tx hash), and notes that the tx hash may be 'undefined' if the account already exists. This enhances understanding of the tool's behavior without contradicting 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?

  The description is front-loaded with the core purpose in the first sentence, followed by implementation details and return values in subsequent sentences. Each sentence adds value without redundancy, making it efficient and well-structured for quick comprehension.

  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?

  Given the tool's complexity (deploying a smart-contract with destructive hint) and lack of output schema, the description provides good coverage: it explains the action, underlying helper, and return values. However, it could benefit from more details on error conditions or deployment prerequisites to be fully complete for a destructive operation.

  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?

  With 100% schema description coverage, the schema fully documents the single parameter 'signer'. The description adds marginal value by reinforcing the parameter's role ('for a given signer') and implying its optional nature, but doesn't provide additional syntax or format details. Since there's only one parameter, the baseline is high, and the description adequately complements 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?

  The description clearly states the specific action ('Deploy a new Abstract Global Wallet') and resource ('smart-contract account') with the target ('for a given signer'). It distinguishes from sibling tools like 'ab_generate_wallet' by specifying this creates a smart-contract account rather than a regular wallet, and from 'ab_deploy_token_erc20' by focusing on wallet deployment versus token deployment.

  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 smart-contract account for a signer, but doesn't explicitly state when to use this tool versus alternatives like 'ab_generate_wallet' for non-smart wallets or other deployment tools. No explicit exclusions or prerequisites are mentioned, leaving some ambiguity about the decision context.

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

• ab_generate_walletA
  4.4/5.0
  Behavior4/5

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

  Annotations provide destructiveHint=false and a title, but the description adds valuable behavioral context beyond that: it discloses security implications ('private key is returned in plaintext'), storage requirements ('Ensure the caller stores it securely'), and logging restrictions ('never logs it'). It doesn't contradict annotations and adds meaningful operational guidance.

  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 perfectly structured with clear sections (RETURNS, COMMON USES, SECURITY), each containing only essential information. Every sentence earns its place: the first states the purpose, subsequent bullets detail outputs and usage context, and the security warning is critical. No wasted words.

  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 0-parameter tool with annotations covering safety (destructiveHint=false) but no output schema, the description provides excellent coverage: purpose, return values (privateKey, address), usage context, and critical security warnings. The only minor gap is not explicitly stating this is a read-only operation (though implied by generation without side effects).

  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?

  With 0 parameters and 100% schema description coverage, the baseline would be 4. The description appropriately doesn't discuss parameters since none exist, and the schema clearly states 'No parameters required.' No additional parameter information is needed or provided.

  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 explicitly states 'Generate a brand-new Externally Owned Account (EOA)' - a specific verb ('Generate') and resource ('EOA'). It clearly distinguishes from sibling tools like ab_agw_create_wallet (likely a different wallet type), ab_deploy_token_erc20 (deployment), ab_get_balance (query), and ab_transfer_token (transaction).

  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 'COMMON USES' section provides clear context: 'Let agents spin up their own keypairs before funding or deploying smart-accounts.' This indicates when to use this tool (pre-funding/pre-deployment) but doesn't explicitly state when NOT to use it or name specific alternatives among siblings.

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

• ab_transfer_tokenA
  4.4/5.0
  Behavior4/5

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

  The description adds valuable behavioral context beyond the destructiveHint annotation. It discloses that the tool performs ENS resolution, automatically fetches token decimals, logs transaction hashes for explorer links, and requires a configured wallet signer. These are practical implementation details not captured in 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?

  The description is efficiently structured with clear sections (FUNCTIONALITY, VALIDATION & LOGGING, COMMON USE-CASES). Each sentence earns its place by providing distinct information without redundancy. The front-loaded purpose statement immediately communicates the core functionality.

  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 destructive tool with no output schema and incomplete parameter documentation, the description does well overall. It covers key behavioral aspects and parameter semantics. However, it doesn't explicitly mention error conditions, gas considerations, or what happens with native ETH transfers (no tokenAddress/tokenSymbol needed), leaving some gaps in completeness.

  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?

  With only 50% schema description coverage (two parameters undocumented), the description compensates well. It explains that tokenAddress or tokenSymbol are needed for ERC-20 transfers, clarifies that amount uses 'human units' (not wei), and mentions ENS support for the 'to' parameter. This adds meaningful context beyond the minimal schema descriptions.

  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 ('transfer value') and resources ('from the caller's wallet to another address'). It distinguishes itself from sibling tools like ab_get_balance (which reads balances) and ab_deploy_token_erc20 (which creates tokens) by focusing on value transfer 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 'COMMON USE-CASES' section provides clear context for when to use this tool (payout rewards, move faucet tokens, automation flows). However, it doesn't explicitly state when NOT to use it or mention specific alternatives among the sibling tools, such as using ab_get_balance first to check funds.

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

• ab_get_balanceA
  4.6/5.0
  Behavior4/5

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

  Annotations provide readOnlyHint=true, and the description reinforces this with 'Read-only operation, no gas spent; safe to run frequently.' It adds valuable context beyond annotations: ENS name resolution capability, human-readable return format, and safety for frequent use. No contradiction with 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?

  The description is well-structured with clear sections (CAPABILITIES, EXAMPLES, RETURNS, SECURITY), front-loaded with the core purpose, and every sentence adds value without redundancy. It efficiently communicates essential information in a compact format.

  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?

  Given the tool's moderate complexity (3 parameters, no output schema), the description is highly complete: it covers purpose, usage, parameters, return format, and security. The only minor gap is lack of explicit error handling or rate limit details, but annotations and context provide sufficient coverage for effective use.

  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?

  Schema description coverage is 100%, so the baseline is 3. The description adds significant value by explaining parameter usage through examples: address accepts ENS names, tokenSymbol uses a lookup table, and tokenAddress is for direct contract specification. This clarifies semantics beyond the schema's basic descriptions.

  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 specific action ('Fetch the current on-chain balance') and resource ('for a wallet'), distinguishing it from sibling tools like create_wallet, deploy_token, generate_wallet, and transfer_token which involve creation, deployment, or transfer operations rather than querying existing balances.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines5/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description provides explicit guidance on when to use this tool: for fetching wallet balances (native ETH or ERC-20 tokens) and when to use specific parameters (tokenAddress vs tokenSymbol). It implicitly distinguishes from siblings by focusing on read-only balance queries rather than write operations like creation or transfers.

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