Server Quality Checklist

Tool Scores

• list_subredditC
  2.9/5.0
  Behavior2/5

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

  With no annotations, the description must disclose behavioral traits. It only states 'public posts' implying read-only scope, but does not explain pagination, default sorting, rate limits, or the meaning of 'approved.' No output format or side effects are described, leaving significant ambiguity.

  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, focused sentence with no redundant words. It conveys the essential purpose immediately and does not bury key information.

  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 four parameters, no annotations, no output schema, and sibling tools, the description is too minimal. It fails to explain what the return value is, how parameters interact, or when to choose this over search_posts. The description alone is insufficient for correct tool invocation.

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

  Parameters1/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 only mentions 'subreddit' indirectly and gives no insight into 'sort', 'limit', or 'time_filter' semantics. The schema itself is detailed, but the description adds no value to parameter understanding.

  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 'List public posts from one approved subreddit' uses a specific verb (List) and resource (public posts) and clearly distinguishes this tool from siblings (search_posts, get_post, get_comments). It is concise and unambiguous about the tool's core function.

  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 explicit usage guidance is provided. The description implies when to use it (to list posts from a subreddit) but does not mention alternatives or exclusions. Sibling tools like search_posts could be confused for this use case, yet there is no differentiation.

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

• search_postsC
  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 behavioral burden. It mentions 'public posts' and 'approved subreddit' as constraints, but does not disclose rate limits, authentication needs, pagination, sorting behavior, or what constitutes 'approved'.

  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 with no fluff. It front-loads the core purpose directly. However, it is under-specified, but that is a completeness issue rather than a conciseness issue.

  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?

  Despite being a search tool with 5 parameters, enums, and no output schema or annotations, the description offers only a terse purpose statement and scope constraint. It does not cover return format, parameter semantics, or operational details, making it incomplete for reliable use.

  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?

  Schema description coverage is 0%, so the description must compensate for parameter meaning. It implicitly hints at 'query' and 'subreddit' by saying 'search posts inside a subreddit', but provides no details about sort, limit, or time_filter, leaving most parameters unexplained.

  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 'Search' and clearly specifies the resource ('public posts') and scope ('inside one approved subreddit'). It distinguishes itself from siblings (list_subreddit, get_post, get_comments) which serve different purposes.

  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 explicit guidance on when to use this tool versus alternatives, nor any exclusions. The phrase 'approved subreddit' implies a prerequisite, but the description does not elaborate on when to choose search_posts over list_subreddit or get_post.

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

• get_commentsB
  3.1/5.0
  Behavior3/5

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

  With no annotations, the description carries the transparency burden. It adds useful behavioral hints ('bounded', 'public', 'approved') but does not disclose default sort/depth/limit behavior, rate limits, or error responses. It provides some value but is 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?

  A single, front-loaded sentence that directly states the tool's purpose. No filler or redundancy, fitting for a straightforward tool.

  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?

  For a 4-parameter tool with no output schema and no annotations, the description is too sparse. It does not clarify what 'bounded' means in practice (the schema shows depth/limit limits but not how they affect results), what 'approved' implies for eligibility, or what the return structure looks like. The description leaves significant gaps.

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

  Parameters1/5

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

  Schema description coverage is 0%, and the description only alludes to post_url ('from an approved Reddit permalink'). It does not explain the meaning or effect of sort, depth, or limit parameters, leaving the agent to infer from the schema alone. This fails to compensate for the lack of schema-level descriptions.

  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 resource ('public comment tree from an approved Reddit permalink'), clearly distinguishing it from siblings like get_post (which would fetch the post itself). It also mentions key scoping constraints (bounded, public, approved).

  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 explicit guidance is given on when to use this tool versus alternatives such as get_post, search_posts, or list_subreddit. The description implies it is for comment trees on a specific post, but does not state exclusions or prerequisites beyond needing a permalink.

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

• get_postA
  3.5/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 'public post' and 'approved permalink' but does not explain what 'approved' means, what happens for unapproved or deleted posts, or what the response includes. The behavioral disclosure is 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, concise sentence that is front-loaded with the main action. It contains no unnecessary words or filler.

  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?

  The tool is simple with one parameter and no output schema, but the description omits details about the approval concept, return format, or error behavior. It is adequate for a basic getter but leaves important context undefined.

  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 has zero description coverage for the parameter 'post_url'. The description adds the term 'permalink' and qualifiers 'approved' and 'public', which provide some context beyond the raw schema, but it does not define what constitutes an approved permalink. Partial compensation for the low schema 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 action ('Get'), the resource ('one public post'), and the source ('approved Reddit permalink'), which distinguishes it from sibling tools like list_subreddit, search_posts, and get_comments. It precisely identifies what this tool does and its scope.

  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 when you have an approved Reddit permalink, but it does not explicitly state when to use this tool versus alternatives or provide exclusion criteria. No alternatives are mentioned, though sibling names give some context.

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