Server Quality Checklist

Tool Scores

• get_recent_transactionsC
  2.9/5.0
  Behavior2/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 states the action but doesn't explain key traits like whether this is a read-only operation, if it requires authentication, rate limits, or what the return format looks like (e.g., list of transactions with details). This leaves significant gaps in understanding how the tool behaves.

  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, efficient sentence that directly states the tool's purpose without any wasted words. It is appropriately sized and front-loaded, making it easy to parse quickly.

  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 the lack of annotations and output schema, the description is incomplete for a tool that retrieves data. It doesn't specify what 'recent' means (e.g., time frame), the structure of returned transactions, or any error conditions, leaving the agent with insufficient context to use the tool effectively.

  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 has 100% description coverage, with the 'limit' parameter well-documented in the schema itself. The description adds no additional meaning beyond implying retrieval of 'recent' transactions, which is already suggested by the tool name. This meets the baseline for high schema coverage without extra value.

  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 resource ('recent transactions for the agent wallet'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_balance' or 'send_usdc', which also involve wallet operations, so it doesn't reach the highest clarity level.

  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 like 'get_balance' or 'send_usdc'. It lacks context about scenarios where retrieving transactions is appropriate, such as for auditing or tracking payments, leaving the agent to infer usage.

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

• request_devnet_airdropA
  3.7/5.0
  Behavior2/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 mentions the tool is for 'free SOL on devnet' and 'testing', which implies it's non-destructive and safe for testing, but lacks details on rate limits, authentication needs, or what happens if the request fails. This leaves gaps in understanding operational constraints.

  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 and highly concise, consisting of two clear sentences that directly state the tool's purpose and usage without any wasted words. Every sentence earns its place by providing essential information efficiently.

  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 low complexity (one optional parameter) and no output schema, the description adequately covers the basic purpose and usage. However, without annotations or output details, it lacks information on behavioral traits like success/failure responses or limitations, making it minimally complete but with gaps for a testing tool.

  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 has 100% description coverage, with the parameter 'amount' documented as 'Amount of SOL to request (max 2)'. The description adds no additional parameter semantics beyond this, such as default values or usage examples. Since the schema does the heavy lifting, 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.

  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 ('Request free SOL on devnet') and resource ('SOL'), distinguishing it from siblings like get_balance or send_usdc by focusing on obtaining test funds rather than querying or sending transactions. It explicitly mentions the purpose 'for testing' and 'for transaction fees', making the intent unambiguous.

  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 this tool ('for testing' and 'to get SOL for transaction fees'), which implicitly differentiates it from siblings used for real transactions or queries. However, it does not explicitly state when not to use it (e.g., for mainnet) or name alternatives, keeping it from a perfect score.

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

• send_usdcA
  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 full burden. It discloses that this executes a real transaction (implying mutation and potential costs/irreversibility) and specifies the network (devnet), which is useful. However, it lacks details on permissions, rate limits, error handling, or transaction confirmation, leaving behavioral aspects 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 front-loaded with the core action and resource, followed by network context, in just two concise sentences. Every word earns its place with no redundancy or fluff, making it highly efficient and easy to parse.

  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 complexity (financial transaction with no annotations and no output schema), the description is minimally adequate. It covers the action and network but lacks details on return values, error cases, or security implications, which are important for a mutation tool in this context.

  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 (recipient, amount, memo) thoroughly. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints, meeting the baseline for high coverage.

  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 ('Send USDC') and target resource ('to another Solana address'), distinguishing it from sibling tools like get_balance or get_recent_transactions which are read-only operations. It explicitly mentions execution on Solana devnet, providing precise scope.

  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 implies usage context by specifying 'real transaction on Solana devnet', suggesting this is for sending funds in a test environment. However, it does not explicitly state when to use this versus alternatives like request_devnet_airdrop for funding or other tools for queries, leaving some guidance gaps.

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

• get_balanceA
  4/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. It discloses the network ('Solana devnet') and return content ('Returns balances'), which are useful behavioral traits. However, it doesn't mention potential limitations like rate limits, authentication requirements, or whether this is a read-only operation (though 'Check' implies non-destructive).

  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 concise with two sentences that each earn their place: the first states the core functionality, and the second adds critical context about the return and network. There's zero wasted language or redundancy.

  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-checking tool with 0 parameters and no output schema, the description provides good context: it specifies which assets (USDC, SOL), whose wallet (agent), and which network (Solana devnet). The main gap is lack of output format details, but given the tool's simplicity and the clear return statement, this is reasonably complete.

  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 0 parameters with 100% schema description coverage, so the schema already fully documents the lack of inputs. The description appropriately doesn't add parameter information, maintaining focus on what the tool does rather than unnecessary details about non-existent 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?

  The description clearly states the specific action ('Check') and resources ('USDC and SOL balance of the agent wallet'), and distinguishes it from siblings like get_recent_transactions (transaction history) and get_wallet_address (address retrieval). It provides exact scope information about which assets and network are involved.

  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 by specifying 'agent wallet' and 'Solana devnet', suggesting this is for checking balances in a development environment. However, it doesn't explicitly state when to use this versus alternatives like send_usdc (for transfers) or request_devnet_airdrop (for funding), nor does it mention any prerequisites or exclusions.

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

• get_wallet_addressA
  4.2/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 implies a read-only operation by using 'Get' and hints at use cases, but does not detail potential errors, authentication needs, or rate limits. This is adequate but lacks depth for a tool in a financial context.

  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 two sentences, front-loaded with the core purpose and followed by a usage guideline. Every word earns its place, with no wasted text, making it highly efficient and easy to parse.

  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 simplicity (0 parameters, no output schema, no annotations), the description is reasonably complete. It explains what the tool does and when to use it. However, it could benefit from more behavioral context, such as error handling or return format, to achieve a score of 5.

  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 input schema has 0 parameters with 100% coverage, so the schema fully documents the lack of inputs. The description does not need to add parameter details, and it appropriately focuses on the tool's purpose without redundancy. A baseline of 4 is applied for zero-parameter tools.

  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 ('Get') and resource ('agent's Solana wallet address'), distinguishing it from sibling tools like get_balance or get_recent_transactions. It provides a concrete purpose that is immediately understandable and differentiated.

  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 states when to use this tool ('to receive funds or share your address'), providing clear context for its application. However, it does not mention when not to use it or explicitly compare it to alternatives like send_usdc, which would be needed for a score of 5.

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