Server Quality Checklist

Tool Scores

• get_wallet_profileA
  3.7/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 bear the full burden. It only describes what the tool does, not its behavioral traits such as read-only status, side effects, caching behavior, or permissions. The force_update parameter hints at caching but the description itself does not address these aspects.

  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 primary action and followed by specific included items. There is no unnecessary content or repetition.

  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?

  With no output schema, the description should clarify the return format but only lists content categories. It lacks information on response structure, potential errors, or how the profile is presented, which is a gap for a complex analysis 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?

  Schema coverage is 100% with detailed parameter descriptions for wallet_address, language, and force_update. The tool description does not add extra meaning beyond the schema, so the baseline 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 states the tool's function with a specific verb ('Analyze') and resource ('a wallet's on-chain behavior'), then lists the output ('investor profile') and its contents. This clearly distinguishes it from sibling tools that focus on digests or market overview.

  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: use this to generate an investor profile for a specific wallet, which is distinct from the sibling tools. However, it does not explicitly mention when not to use it or alternative tools, so it lacks explicit exclusions.

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

• get_personalized_digestA
  3.8/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 for behavioral disclosure. It describes the returned content (holdings analysis, news, recommendations) but does not explicitly state this is a read-only operation, mention error behavior, or address privacy implications of sending a wallet address. The verb 'Get' implicitly suggests a read-only action.

  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 concise—two sentences, front-loaded with the main action, and no superfluous wording. Every phrase adds value by explaining purpose or content.

  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 two-parameter tool with no output schema, the description sufficiently covers what the digest includes and the basis for personalization. It could mention error handling for invalid wallets or clarify relationship to sibling tools, but schema and context signals cover most gaps.

  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% for both parameters, so the baseline is 3. The description references 'wallet's on-chain behavior' which maps to wallet_address, but adds no new parameter details beyond what the schema already provides. Language parameter is fully described via enum and default in 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 tool's function: 'Get personalized Web3 digest' based on wallet's on-chain behavior. It uses a specific verb and resource, and the emphasis on 'personalized' and 'wallet's on-chain behavior' distinguishes it from sibling tools like get_public_digest.

  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 (when a personalized digest is needed) but does not explicitly state when to use this tool versus alternatives like get_public_digest or get_wallet_profile. No exclusions or alternative recommendations are provided.

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

• get_public_digestA
  4/5.0
  Behavior3/5

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

  With no annotations, the description carries the full burden. It discloses the public nature and lack of personal data, which is useful, but doesn't mention any auth requirements, rate limits, or return format. For a simple read tool, it provides adequate but not rich behavioral 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?

  Two concise sentences, front-loaded with the primary action and content. No wasted words; effectively structured.

  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?

  The tool has one optional parameter and no output schema. The description covers the digest content well and implies a read-only operation. It lacks explicit return format details, but for a simple public digest, the description is complete enough.

  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 schema fully describes the single parameter (language) with enum and default. The description adds no extra parameter semantics, but schema coverage is 100%, so baseline 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 tool retrieves 'today's Web3 public digest' with specific content types (macro news, KOL sentiment, market data). The word 'public' and 'No personal data required' directly differentiate it from get_personalized_digest, and the content list distinguishes it from market overview and wallet profile.

  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 for general public digest needs without personalization, explicitly noting 'No personal data required'. While it doesn't name alternative tools, the 'public' vs 'personalized' contrast provides clear context for when to choose this tool.

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

• get_market_overviewA
  4.2/5.0
  Behavior4/5

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

  With no annotations, the description carries the full burden. It clearly states what the tool returns: current BTC/ETH prices and Fear & Greed Index. It implies a read-only operation with no side effects, providing adequate transparency for a simple getter with zero parameters.

  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, tight sentence that conveys all essential information without redundancy. Every word adds value, making it perfectly concise and well-structured.

  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 (no parameters, no output schema), the description is complete enough. It specifies the exact data returned and implies a one-shot call. It doesn't mention return format or limitations, but these are not necessary for such a basic tool.

  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 zero parameters, so the schema is complete with 100% coverage. The baseline for 0 params is 4, and the description adds no param-specific detail because none is needed. It appropriately avoids inventing parameter semantics that don't exist.

  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') and specific resource ('crypto market overview') with concrete components (BTC/ETH prices and Fear & Greed Index). This unequivocally distinguishes it from siblings like get_public_digest and get_wallet_profile, which serve different purposes.

  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 use case (when you need crypto market overview) but provides no explicit guidance on when to choose this tool over alternatives, nor any exclusions or prerequisites. Sibling names suggest distinct purposes, but no direct comparison is given.

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