Server Quality Checklist

Tool Scores

• get_reddit_post_detailsC
  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. It mentions that it returns 'human readable string containing detailed post information', which gives some behavioral context about the output format. However, it lacks details on error handling, rate limits, authentication needs, or what 'detailed information' includes beyond the schema.

  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 appropriately sized and front-loaded with the core purpose in the first sentence. The 'Args' and 'Returns' sections are structured but could be more integrated. There's minimal waste, though the 'human readable string' note might be redundant if the output schema exists.

  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 low complexity (1 parameter) and the presence of an output schema, the description is somewhat complete but has gaps. It covers the basic purpose and parameter, but without annotations, it should ideally include more behavioral context like error cases or usage distinctions from siblings.

  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 0%, so the description must compensate. It adds that 'post_id' is 'The Reddit post ID', which provides basic semantics beyond the schema's title 'Post Id'. However, it doesn't explain format (e.g., alphanumeric string), examples, or constraints, leaving gaps in parameter understanding.

  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 ('Get') and resource ('detailed information about a specific Reddit post'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_hot_reddit_posts' or 'search_reddit_posts', which prevents a perfect score.

  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. With sibling tools like 'search_reddit_posts' and 'get_hot_reddit_posts' available, there's no indication that this tool is for retrieving details of a known post ID rather than searching or listing posts.

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

• get_subreddit_infoC
  2.9/5.0
  Behavior2/5

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

  With no annotations provided, the description carries full burden but offers minimal behavioral context. It mentions the return format ('Human readable string') but doesn't disclose authentication needs, rate limits, error conditions, or whether it's a read-only operation. The description is functional but lacks important operational details.

  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 appropriately sized and well-structured with clear sections for Args and Returns. The main purpose is stated upfront, and the parameter documentation is concise. The structure helps with readability, though the 'Human readable string' return description could be more specific.

  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 has an output schema (though not shown), the description doesn't need to detail return values. However, with no annotations and minimal behavioral disclosure, the description is adequate but incomplete. It covers the basic purpose and parameter but lacks context about when to use it versus siblings and operational considerations.

  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 0%, but the description provides clear parameter semantics: 'The name of the subreddit (without r/)'. This adds valuable context beyond the bare schema. However, with only one parameter, the baseline would be 4 if no param info was provided; the description adds some value but doesn't fully compensate for the lack of schema descriptions.

  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 ('Get') and resource ('information about a subreddit'). It distinguishes from siblings by focusing on subreddit metadata rather than posts or search, though it doesn't explicitly contrast with sibling tools.

  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?

  No guidance is provided on when to use this tool versus alternatives like get_hot_reddit_posts or search_reddit_posts. The description only states what it does, not when it's appropriate or what distinguishes it from similar tools.

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

• get_hot_reddit_postsB
  3.2/5.0
  Behavior2/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 mentions the return format ('Human readable string') but lacks critical details: whether authentication is required, rate limits, error handling, or what 'hot' means algorithmically. For a tool with zero annotation coverage, this leaves significant gaps in understanding its 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 efficiently structured with a clear purpose statement followed by Args and Returns sections. Every sentence adds value: the first states the action, and the subsequent lines provide essential parameter and output details without redundancy. It's front-loaded and appropriately sized for the tool's complexity.

  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 has an output schema (implied by 'Has output schema: true'), the description doesn't need to detail return values. However, with no annotations and 2 parameters, it partially compensates with parameter semantics but lacks behavioral context like authentication or rate limits. For a simple read operation, it's adequate but has clear gaps in completeness.

  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 description adds meaningful context beyond the input schema, which has 0% description coverage. It explains that 'subreddit' excludes the 'r/' prefix and provides default and max values for 'limit', which aren't in the schema. This compensates well for the low schema coverage, though it doesn't detail parameter constraints like valid subreddit formats.

  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 verb 'Get' and resource 'hot posts from a subreddit', making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_subreddit_info' or 'search_reddit_posts', which might also retrieve subreddit content. The purpose is specific but lacks sibling distinction.

  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 like 'search_reddit_posts' or 'get_subreddit_info'. It mentions what the tool does but offers no context about when it's appropriate, such as for trending content versus general searches, or prerequisites like authentication needs.

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

• search_reddit_allB
  3.2/5.0
  Behavior2/5

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

  With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the return format ('Human readable string containing search results') but doesn't cover important aspects like rate limits, authentication requirements, error conditions, or whether this is a read-only operation. The description is minimal 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 well-structured and efficiently organized. It starts with the core purpose, then provides a clear Args section with bullet-point style documentation for each parameter, followed by a Returns section. Every sentence adds value with no wasted words.

  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 has 4 parameters with no schema descriptions and an output schema exists, the description does a good job documenting parameters but is light on behavioral context. For a search tool with sibling alternatives, more guidance on usage context would be beneficial. The existence of an output schema means the description doesn't need to detail return values.

  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 description provides excellent parameter documentation with clear explanations for all 4 parameters, including defaults, ranges, and allowed values. With 0% schema description coverage, the description fully compensates by adding comprehensive semantic information beyond what the bare schema provides.

  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: 'Search for posts across all of Reddit (site-wide search)'. This specifies the verb (search), resource (posts), and scope (all of Reddit). However, it doesn't explicitly differentiate from sibling tools like 'search_reddit_posts', which might have different scope or functionality.

  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. With sibling tools like 'search_reddit_posts' and 'get_hot_reddit_posts', there's no indication of when this site-wide search is preferred over other search or listing methods.

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

• search_reddit_postsB
  3.3/5.0
  Behavior2/5

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

  With no annotations provided, the description carries full burden for behavioral disclosure. It mentions default values and limits, which is helpful, but doesn't cover important aspects like rate limits, authentication requirements, error conditions, or pagination behavior. For a search tool with no annotation coverage, this leaves significant 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 well-structured and efficiently organized. It starts with a clear purpose statement, then provides a parameter table with essential details, and ends with return information. 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?

  Given the tool's moderate complexity (5 parameters, no annotations, but has output schema), the description is fairly complete. It documents all parameters thoroughly and mentions the return format. The output schema existence means it doesn't need to detail return values. The main gap is lack of behavioral context like rate limits or error handling.

  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 description provides excellent parameter documentation with clear explanations of each parameter's purpose, default values, and constraints. With 0% schema description coverage, this fully compensates by adding meaning beyond what the bare schema provides. The only minor gap is not explicitly stating that 'subreddit' should be provided without the 'r/' prefix.

  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: 'Search for posts in a specific subreddit' - a specific verb ('search') and resource ('posts in a specific subreddit'). It doesn't explicitly distinguish from sibling tools like 'search_reddit_all' (which searches all of Reddit vs. a specific subreddit), but 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 Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  No guidance is provided on when to use this tool versus alternatives like 'search_reddit_all' (for searching across Reddit) or 'get_hot_reddit_posts' (for getting hot posts without a query). The description only states what the tool does, not when it's appropriate relative to siblings.

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