Server Quality Checklist

Tool Scores

• search_redditA
  3.6/5.0
  Behavior3/5

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

  Annotations already declare readOnlyHint=true. The description adds that it returns 'content and metadata', which provides some behavioral context but lacks details on rate limits, authentication needs, or pagination behavior. Adequate given annotations.

  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 concise sentence with no fluff. It could be slightly expanded to include more guidance on parameter usage without losing conciseness.

  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 7 parameters and no output schema, the description covers the basic purpose but misses operational details like sort/time defaults, limit constraints, and how to use optional filters like flair and author. Adequate for a search tool but has gaps.

  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 43% (3 of 7 parameters have descriptions). The description does not add meaning beyond what the schema provides for parameters like sort, time, flair, and author. Baseline 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 the verb 'Search', the resource 'posts', and the scope 'across Reddit or specific subreddits'. It effectively differentiates from sibling tools like browse_subreddit (browsing, not searching) and get_post_details (single post).

  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 for searching posts but does not explicitly state when to use this tool vs alternatives like browse_subreddit or reddit_explain. No exclusions or when-not scenarios are mentioned.

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

• reddit_explainA
  4.1/5.0
  Behavior3/5

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

  Annotations provide readOnlyHint=true, and description adds return content details (definition, origin, usage, examples). However, no disclosure of rate limits, authentication needs, or potential errors. Description is consistent with annotations.

  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 sentences: first states purpose and action, second lists return elements. No redundant phrasing, front-loaded with key information.

  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 tool with one parameter and no output schema, the description fully explains what the tool does and what it returns. The sibling tools cover other use cases, so no need for additional context.

  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?

  Input schema covers the single 'term' parameter with 100% description coverage. The description adds concrete examples (e.g., 'karma', 'cake day', 'AMA'), enhancing understanding beyond the schema alone.

  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?

  Description clearly states the verb 'Get explanations' and specifies the resource: 'Reddit terms, slang, and culture.' It lists return components (definition, origin, usage, examples) and distinguishes this tool from siblings like browse_subreddit or search_reddit.

  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 use for explaining terms but does not explicitly state when to use this tool versus alternatives. No mention of when not to use or conditions for use, leaving the agent to infer context from the sibling list.

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

• user_analysisA
  4.2/5.0
  Behavior4/5

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

  Annotations include readOnlyHint=true, and the description aligns with that. Additional behavioral details are provided in the parameter description (time_range sorting behavior) but no further safety or side-effect context beyond what annotations already convey.

  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-loading the purpose with no superfluous information. Every word serves a clear function.

  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 absence of an output schema, the description provides a reasonable overview of what is returned (posts, comments, statistics). However, it could be more explicit about the exact statistics or structure returned.

  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 documents parameters. The tool description adds no extra parameter insights beyond the schema, but includes a helpful note on time_range sorting behavior in the parameter description itself.

  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 'Analyze a Reddit user's posting history, karma, and activity patterns' with a specific verb and resource. It distinguishes from siblings like browse_subreddit or search_reddit by focusing on a single user's data.

  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 (when analyzing a user), but it does not explicitly state when not to use or mention alternatives. However, sibling names provide implicit differentiation.

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

• browse_subredditA
  4.4/5.0
  Behavior5/5

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

  Beyond the readOnlyHint annotation, the description discloses the data_source field behavior, null fields when using RSS, and warns not to infer popularity from RSS data. This gives full transparency on credential-dependent output differences.

  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 sentences efficiently cover purpose and credential behavior. Every sentence adds value; no redundant or vague wording.

  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 explains the return structure, credential dependency, and field differences. It lacks details on pagination (e.g., how to get more than limit results) but given no output schema and basic read operation, this 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?

  The description adds minimal extra meaning beyond the schema: it mentions sort choices in text, but does not elaborate on 'time', 'include_nsfw', or 'include_subreddit_info'. With 50% schema description coverage, the description does not fully compensate, though it provides context on credential effects.

  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 fetches posts from a subreddit with sorting options, and the return includes a data_source field. This distinguishes it from sibling tools like search_reddit (searching across Reddit) and get_post_details (single post).

  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 explains how results differ based on Reddit credentials, guiding when each behavior applies. It does not explicitly state when not to use this tool versus alternatives, but the context from sibling names and the description itself implies browsing vs searching.

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

• get_post_detailsA
  4.6/5.0
  Behavior4/5

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

  Annotations already declare readOnlyHint=true. Description adds value by detailing extra API call behavior and efficiency gains with subreddit, which annotations lack.

  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?

  Three sentences, front-loaded with purpose, then requirements, then an important efficiency note. 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?

  Covers key behavioral aspects for 8 parameters and no output schema. Includes efficiency and required argument strategies, though lacks detail on return format or extract_links.

  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 coverage is 75%; description enhances understanding by explaining the trade-off between url and post_id parameters, and the efficiency benefit of providing subreddit.

  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?

  Clearly states 'Fetch a Reddit post with its comments', specifying verb and resource. Differentiates from sibling tools like browse_subreddit and search_reddit.

  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?

  Explicitly requires url OR post_id, and advises providing subreddit for efficiency. Provides clear context on when and how to use, with an alternative strategy.

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