Server Quality Checklist

Tool Scores

• check-healthA
  3.6/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 describes what the tool returns (uptime, model info, pricing) which is helpful context. However, it doesn't disclose important behavioral aspects like whether this is a read-only operation, potential rate limits, authentication requirements, or error conditions. The description adds some value but leaves significant behavioral gaps.

  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 - a single sentence that communicates the complete purpose and return information without any wasted words. It's front-loaded with the primary function ('check if the AgentOracle API is online') followed by the specific data returned. Every word earns its place.

  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 simplicity (0 parameters, no output schema, no annotations), the description is reasonably complete for a health check tool. It explains what information is returned. However, without annotations or output schema, it should ideally provide more detail about the response format, error handling, or when this tool should be preferred over similar status-checking operations. The description is adequate but could be more comprehensive.

  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 with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't waste space discussing parameters that don't exist, which is efficient and correct. No additional parameter semantics are needed or provided.

  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 tool's purpose with specific verbs ('check if... is online', 'get service status') and resources ('AgentOracle API'). It distinguishes itself from sibling tools like 'deep-research' and 'research' by focusing on health/status rather than research operations. However, it doesn't explicitly differentiate from 'get-manifest' which might also provide system information.

  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 you need to verify API availability and obtain service metrics. However, it doesn't provide explicit guidance on when to use this versus alternatives like 'get-manifest', nor does it specify prerequisites or exclusions. The usage context is reasonably clear but lacks explicit comparison with sibling tools.

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

• get-manifestA
  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 return content (payment requirements, networks, pricing, endpoint details) but doesn't mention behavioral aspects like rate limits, authentication requirements, or whether this is a cached/static response versus dynamic data.

  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 efficient sentences that front-load the core purpose and follow with specific return details. Every word earns its place with zero redundancy or unnecessary elaboration.

  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 zero-parameter read-only tool with no output schema, the description provides good context about what information is returned. However, it could be more complete by mentioning whether this is static configuration data or requires authentication, given the lack of annotations.

  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 with 100% schema coverage, so the baseline is 4. The description appropriately doesn't waste space discussing nonexistent parameters and focuses on what the tool returns instead.

  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 ('AgentOracle x402 payment manifest'), and distinguishes it from sibling tools by specifying it returns payment integration details rather than health checks or research functions.

  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 (programmatic integration needs) but doesn't explicitly state when to use this tool versus alternatives like check-health or research tools. No explicit exclusions or comparisons are provided.

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

• researchA
  4.2/5.0
  Behavior4/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 effectively describes key behavioral traits: the tool performs real-time research, returns structured results with specific components (summary, key facts, cited sources, confidence score), and has a cost of $0.02 USDC per query via x402 on Base mainnet. This covers important operational aspects beyond basic functionality.

  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 in two sentences that each earn their place: the first explains the core functionality and output format, the second discloses the cost mechanism. There's zero wasted text and it's appropriately front-loaded with the most important information.

  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 single-parameter tool with no annotations and no output schema, the description provides substantial context about behavior, output format, and cost. It could be slightly more complete by explicitly mentioning the 'deep-research' sibling tool alternative, but overall it's quite comprehensive given the tool's complexity level.

  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 description coverage is 100% with comprehensive documentation of the single 'query' parameter including examples. The description doesn't add any parameter-specific information beyond what's already in the schema, so it meets the baseline expectation when the 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 ('perform real-time research'), resource ('any topic using AgentOracle'), and distinguishes from siblings by specifying the structured result format and cost mechanism. It goes beyond just restating the name 'research' to explain what the tool actually does.

  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 about when to use this tool ('perform real-time research on any topic') and mentions the cost per query, which helps users understand usage implications. However, it doesn't explicitly differentiate when to use this versus the 'deep-research' sibling tool, which appears to be a related alternative.

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

• deep-researchA
  4.4/5.0
  Behavior4/5

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

  With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: the specific return format (10-15 facts, analysis paragraph, sources, confidence score), payment requirement ($0.10 USDC via x402), and that it's for complex topics. It doesn't mention rate limits or error conditions, keeping it from a perfect score.

  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 and front-loaded: the first sentence states the core purpose, subsequent sentences add crucial details (output format, cost, usage context). Every sentence earns its place with 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 single-parameter tool with no annotations and no output schema, the description provides excellent context about behavior, outputs, and usage. It falls short of perfect because it doesn't explicitly describe error cases or response structure details, though the output format is well-specified.

  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 fully documents the single 'query' parameter. The description adds no additional parameter semantics beyond what's in the schema, maintaining the baseline score of 3 for adequate but not enhanced 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 tool's purpose with specific verbs ('perform comprehensive deep research') and resource ('any topic using AgentOracle Sonar Pro'). It distinguishes from the sibling 'research' tool by emphasizing 'comprehensive' analysis with specific outputs (10-15 facts, analysis paragraph, sources, confidence score).

  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?

  Explicit guidance is provided on when to use this tool ('for complex topics requiring thorough analysis') and when not to use it (implied: simpler topics should use the sibling 'research' tool). The cost disclosure ($0.10 per query) also helps determine appropriate usage contexts.

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