Server Quality Checklist

Tool Scores

• search_redditA
  3.9/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 payload (title, body, url, engagement stats) and the optional subreddit restriction, but does not mention sorting, pagination, or rate limits. This is adequate but not rich.

  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: the first states the primary action and optional restriction, the second states the return fields. No unnecessary words or redundancy.

  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?

  For a simple search tool with comprehensive parameter documentation, the description provides sufficient context: it covers the purpose, optional scope, and return fields. No output schema exists, but stating the returned fields is adequate for agent invocation.

  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% with detailed parameter descriptions including defaults, enums, and examples. The description adds no parameter semantics beyond what the schema already provides, so the baseline of 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 that the tool searches Reddit for recent posts matching a query, optionally restricted to subreddits. This specific verb+resource combination distinguishes it from sibling tools like fetch_thread, which retrieves a specific thread.

  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 usage context is implied: use this when you need to discover recent Reddit posts. However, no explicit guidance is provided about when to prefer this over alternatives like fetch_thread, and no exclusions or prerequisites are mentioned.

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

• fetch_threadA
  4.2/5.0
  Behavior4/5

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

  No annotations are provided, so the description carries the burden of behavioral disclosure. It discloses that the tool fetches the post and its top comments, and implies a read-only operation. It does not mention return format or potential limits (e.g., max_comments), but the schema covers the limit and the description provides the core behavior.

  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, front-loaded sentence that immediately states the action and purpose. Every word contributes value; there is no redundancy or filler.

  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 (2 parameters, 1 required) and lack of output schema, the description plus schema provide sufficient context. It covers what the tool does and when to use it. It does not detail the exact response structure, but for a read-only fetch with clear parameters, that is acceptable.

  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 describes 'url' and 'max_comments' (including default and range). The description adds minimal semantic value beyond reinforcing that 'top comments' are included, but it does not clarify parameter syntax or edge cases beyond 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 verb ('Fetch'), the resource ('a Reddit post with its top comments'), and the use case ('before drafting a reply'). It is easily distinguished from sibling tools 'search_reddit' and 'score_leads' since it retrieves a specific known thread rather than searching or scoring.

  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 gives explicit context for when to use the tool: 'before drafting a reply' (i.e., when you need the full conversation for a known post). It does not explicitly list exclusions or mention alternatives, but the sibling context makes the intended usage clear.

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

• score_leadsA
  4.4/5.0
  Behavior5/5

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

  With no annotations provided, the description carries full burden and excels: it discloses the two-phase scoring (lexical pre-score then Claude semantic), the ANTHROPIC_API_KEY requirement, the fallback behavior without the key, and the final sort order. This is rich behavioral context beyond basic safety.

  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 purpose, then details the process and key constraints. Every clause adds value—no filler. It is highly 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?

  The description covers the main flow, the API dependency, fallback, and sort order. However, with no output schema, it does not specify the exact format of the final score (e.g., field name, range), leaving a small gap. For a tool of this complexity, this is a minor omission.

  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%, so the baseline is 3. The description adds context about the escalation threshold and two-phase process, but all parameter meanings are already well documented in the schema (e.g., 'Pre-score needed before a post is sent to Claude'). The description does not add significant new semantics beyond the 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 specific function: 'Score Reddit posts as sales leads for a product' with a detailed two-phase process and return behavior. This verb+resource combination clearly distinguishes it from siblings like search_reddit and fetch_thread.

  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 when to use by stating it scores posts 'as sales leads' and the schema's posts parameter notes they come 'as returned by search_reddit', giving clear context. However, it lacks explicit exclusions or direct alternatives, so it doesn't fully meet the 5-level bar.

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