Server Quality Checklist

Tool Scores

• get_payment_infoA
  3.9/5.0
  Behavior3/5

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

  No annotations are provided, so the description bears full burden. It implies a read-only retrieval operation with no side effects, but does not mention authorization, rate limits, or any behavioral nuances. For a simple getter with zero parameters, the disclosure is adequate but minimal.

  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 11 words, front-loading the core action and resource. Every word earns its place; no redundancy or fluff.

  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 no output schema and no annotations, the description could be more explicit about the structure of the returned data (e.g., format of URLs, whether both tiers are returned in a single response). However, for a zero-parameter tool of low complexity, the current description provides a functional minimum.

  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 description does not need to add parameter info. The schema coverage is vacuously 100%. Baseline for 0 params is 4, and the description correctly focuses on the tool's output, adding no confusion.

  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 clearly identifies the resources: 'payment URLs and USDC wallet address'. It also specifies scope ('for both audit tiers'), which distinguishes it from sibling tools that deal with brand audits and geographic checks. The purpose is unambiguous.

  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?

  No explicit guidance on when to use this tool versus alternatives. The description implies it is for retrieving payment info, but does not state when not to use it or provide comparative context. The simplicity of the tool (no parameters) makes this gap minor.

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

• geo_quick_checkA
  4.6/5.0
  Behavior4/5

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

  With no annotations, the description carries full burden. It discloses key behaviors: it is a single-source search (5 results), costs $0.05 USDC, and returns a payment link if no token is provided. However, it does not mention what happens on error (e.g., invalid brand or token) or any rate limits, but the transparency is adequate for a simple read-oriented tool.

  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 extremely concise—two sentences that front-load the core purpose and output, then directly contrast with the sibling tool. Every sentence adds essential information without 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?

  The tool is simple and lacks an output schema, but the description lists the expected return elements (score, URLs, tips). It is complete enough for an agent to understand what the tool does and what it yields. Minor gaps like error handling or result format details are acceptable given the tool's simplicity.

  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% (both parameters have descriptions). The description adds value beyond schema by explaining the paymentToken fallback behavior ('If omitted, the tool returns a payment link') and implicitly connecting the query to a brand name, but the schema already handles the basic semantics well.

  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: a quick brand visibility snapshot across LLM-indexed sources, returning a score, top 3 citations, and 2 tips. It also distinguishes from the sibling 'audit_brand' by emphasizing it's a single-source search with limited results and a lower cost, making the purpose unambiguous.

  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 explicitly tells the agent when to use this tool ('quick snapshot') and when to use the sibling 'audit_brand' for full citations and recommendations. It also notes the payment requirement and provides the fallback behavior (returns payment link if token omitted), offering clear guidance on invocation context.

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

• audit_brandA
  4.7/5.0
  Behavior5/5

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

  No annotations provided, so description carries full burden. It discloses the cost ($1.50 USDC), the return values, and the behavior when paymentToken is omitted (returns payment link). This is comprehensive for a read-only audit tool.

  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 with no wasted words. First sentence covers purpose and output, second adds cost and alternative. Information density is high and well-organized.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness5/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Despite no output schema, the description lists all return components (visibility score, label, citations, index status, GEO recommendations). It also covers payment flow and alternative tool. Completeness is high.

  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 coverage is 100% (baseline 3). The description adds value beyond schema by explaining the query parameter with examples and clarifying the paymentToken role. This justifies a higher score.

  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 performs a 'Full brand visibility audit across LLM-indexed sources (Brave + Exa, 10 results).' It differentiates from sibling tool 'geo_quick_check' by specifying the scope and depth.

  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?

  Explicitly suggests using 'geo_quick_check' for a quick snapshot at lower cost, providing clear context for when to choose this tool. Could further state when not to use it (e.g., for non-LLM sources) but is adequate.

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