Server Quality Checklist

Tool Scores

• inspect_tokenB
  3.2/5.0
  Behavior2/5

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

  No annotations are provided, so the description carries the full disclosure burden. The verb 'check' implies a read-only analysis operation, but the description does not disclose what specific checks are performed, whether external calls are made, whether the operation is safe and non-mutating, or what the result contains. The word 'comprehensive' promises breadth without specifying it — a meaningful gap for an inspection tool.

  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?

  A single 12-word sentence with zero filler. The core action is front-loaded and the structure is clean. It loses one point only because the brevity sacrifices informative content that would have helped behavioral transparency and contextual completeness.

  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?

  The tool signature is simple — two well-documented parameters, one enum-constrained — so the schema carries most of the invocation burden. However, with no output schema and no annotations, the agent has no idea what a 'comprehensive security and liquidity check' returns or what criteria it evaluates. The vague 'comprehensive' leaves a notable gap given the absence of output documentation.

  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%: both contractAddress and chain are already documented, and chain has an enum restricting valid networks. The description adds no parameter-level meaning beyond the schema, which is acceptable given the high coverage baseline of 3.

  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 states a clear verb ('Perform'), a specific resource ('cryptocurrency token contract'), and the nature of the operation ('security and liquidity check'). It effectively communicates the tool's domain. However, the qualifier 'comprehensive' is vague — it does not enumerate what security or liquidity checks are actually performed — which keeps this from a 5.

  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?

  There are no sibling tools, so there is no need for exclusionary routing. The phrase 'security and liquidity check' implies the usage context of vetting a token before interacting with it, but no explicit when-to-use guidance is provided. The usage scenario is only implied, not stated.

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