Server Quality Checklist

Tool Scores

• roll_diceC
  2.4/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 burden of behavioral disclosure. It mentions the action ('Roll the dice') but doesn't describe what happens during execution, such as whether it's deterministic, random, or has side effects like logging. It also doesn't cover output format, error handling, or any constraints like rate limits. The description adds minimal behavioral context beyond the basic action.

  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?

  The description is a single, efficient sentence that directly states the tool's action. It's front-loaded with the main purpose and avoids unnecessary words. However, it could be more structured by including key details, but as is, it's appropriately concise for its limited content.

  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 tool has 2 parameters with 0% schema coverage, no annotations, and no output schema, the description is incomplete. It doesn't explain the dice rolling behavior, parameter meanings, or what to expect as a result. For a tool that likely involves randomness and specific input formats, more context is needed to guide the agent effectively.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters2/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The schema description coverage is 0%, so the description must compensate for the lack of parameter documentation. It mentions 'notation' but doesn't explain what it is (e.g., dice notation like '2d6'), and it doesn't address 'num_rolls' at all. The description adds little meaning beyond what the schema's titles provide, failing to clarify parameter usage or examples.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose3/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description states the action ('Roll the dice') and mentions the input ('with the given notation'), which gives a vague purpose. However, it doesn't specify what 'notation' means or what kind of dice rolling this involves (e.g., standard dice, RPG dice), and it doesn't differentiate from siblings like 'get_crypto_price' or 'web_search', which are unrelated tools. The purpose is understandable but lacks specificity.

  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. It doesn't mention any context, prerequisites, or exclusions, such as when dice rolling is appropriate compared to other tools on the server. Without any usage instructions, the agent must infer based on the tool name alone.

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

• web_searchC
  2.9/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 burden of behavioral disclosure. It states the tool searches the web but doesn't disclose any behavioral traits such as rate limits, authentication needs, result formats, pagination, or potential side effects. This leaves significant gaps for an AI agent to understand how the tool behaves beyond its basic function.

  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's appropriately sized and front-loaded, making it easy to parse quickly. Every part of the sentence contributes to understanding the tool's function.

  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 complexity of a web search tool with no annotations, no output schema, and low parameter documentation (0% schema coverage), the description is incomplete. It lacks details on behavioral aspects, result handling, and parameter usage, which are crucial for effective tool invocation by an AI agent 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?

  The description adds minimal meaning beyond the input schema. It mentions 'the given query', which aligns with the single 'query' parameter in the schema, but schema description coverage is 0%, so the schema provides no details about the parameter. The description doesn't compensate by explaining query syntax, length limits, or examples, leaving the parameter semantics largely undocumented.

  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 a specific verb ('Search') and resource ('the web'), and specifies the action is about 'information about the given query'. It's not tautological and distinguishes itself from siblings like get_crypto_price and roll_dice by focusing on general web search rather than specific data retrieval or random generation.

  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. It doesn't mention any context, exclusions, or comparisons with sibling tools like get_crypto_price for cryptocurrency data or roll_dice for random number generation. Usage is implied only by the general purpose stated.

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

• get_crypto_priceB
  3.1/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 burden of behavioral disclosure. It mentions the tool returns a 'Formatted string with current price and market data,' which gives some output context, but lacks details on error handling, rate limits, authentication needs, or data freshness. For a tool with no annotations, this is a significant gap in transparency.

  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?

  The description is well-structured and appropriately sized, with a clear purpose statement followed by Args and Returns sections. Every sentence adds value, and it's front-loaded with the core functionality. Minor room for improvement in brevity, but it's efficient overall.

  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 moderate complexity (2 parameters, no output schema, no annotations), the description is somewhat complete but has gaps. It covers purpose and parameters well but lacks behavioral details like error cases or rate limits. Without annotations or output schema, it should do more to guide the agent, making it adequate but not fully 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?

  Schema description coverage is 0%, so the description must compensate. It effectively explains both parameters: 'coin_id' as 'The cryptocurrency ID (e.g., 'bitcoin', 'ethereum', 'dogecoin')' and 'vs_currency' as 'The currency to compare against (default: 'usd')'. This adds clear meaning beyond the bare schema, covering semantics and examples, though it could note parameter constraints like valid currency codes.

  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: 'Get the current price and market data for a cryptocurrency.' It specifies the verb ('Get') and resource ('current price and market data for a cryptocurrency'), making it easy to understand. However, it doesn't differentiate from sibling tools like 'roll_dice' or 'web_search', which is unnecessary here since they serve completely different domains, so a 4 is appropriate.

  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. It doesn't mention any context-specific scenarios, prerequisites, or exclusions. While the sibling tools are unrelated, there's no explicit or implied usage advice, leaving the agent without operational context.

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