Server Quality Checklist

Tool Scores

• get_trendsC
  2.7/5.0
  Behavior2/5

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

  With no annotations provided, the description must convey behavioral traits. It only says 'current' trends, implying real-time data, but does not disclose whether the operation is read-only, any rate limits, or what the response structure looks like. No mention of pagination, sorting, or default behavior beyond the schema's defaults. The description adds minimal value beyond the obvious action.

  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 with no extraneous information. Every word contributes to stating the tool's core function. This is an example of efficient, concise specification.

  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 there is no output schema and no annotations, the description should cover behavior and return expectations. It only states 'get current trends', but does not describe what the output looks like, any specific behaviors (e.g., current trends for a region), or limitations. The description is not complete enough for an agent to understand the tool's full usage without further guesswork.

  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?

  The schema has two parameters (limit, region) with 0% description coverage, and the tool description provides no additional meaning for them. It does not explain what 'region' accepts (e.g., codes, names) or how 'limit' behaves. The description's phrase 'for a region' hints at the region parameter but gives no format or constraints. This is insufficient compensation for the schema's lack of 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: 'Get current X trends for a region'. It identifies the specific resource (trends) and the action (get), which is clear even without comparing to siblings. It doesn't explicitly differentiate from sibling tools like search_tweets or x_search, but the verb+resource combination is unambiguous enough to warrant a 4.

  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?

  There is no guidance on when to use this tool versus the sibling tools (search_tweets, fetch_tweet, x_search_status, x_search). The description merely states what it does, without any context for selection or exclusion criteria. This is a clear lack of usage guidance.

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

• x_searchC
  2.8/5.0
  Behavior3/5

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

  The description explicitly labels the tool as 'read-only', which is a useful behavioral signal, especially since no annotations are provided. However, it fails to disclose other important behaviors like return format, pagination, rate limits, or authentication requirements.

  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 that is front-loaded with the key purpose. It avoids fluff, though its brevity limits the information conveyed.

  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?

  With 7 parameters, no output schema, and no annotations, the description carries a heavy burden. It only provides a high-level purpose and the read-only hint, leaving out essential details about result types, filter semantics, or how it relates to sibling tools.

  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 71%, so the schema already documents most parameters. The description adds no extra semantic detail about parameter values or usage; it only mentions 'free-form' which hints at query flexibility but doesn't elaborate beyond the schema.

  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 says 'Free-form read-only X/Twitter research' which conveys a search-like purpose but is vague about what type of results are returned. It doesn't clearly differentiate from sibling tool 'search_tweets', which likely has a more specific search scope.

  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. It doesn't mention 'search_tweets' or any other sibling, nor does it describe suitable use cases, exclusions, or prerequisites.

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

• search_tweetsB
  3.2/5.0
  Behavior2/5

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

  Without annotations, the description carries the full transparency burden but only notes that results are 'recent' and lists filters. It does not disclose pagination, result limits, rate limits, or return format, leaving significant behavioral 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, front-loaded sentence that mentions the core action (search), resource (recent X posts), and optional filters without wasted words.

  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?

  The tool has no annotations or output schema, so the description should explain return values and usage context more fully. It omits result details, pagination, and any guidance relative to sibling search tools, leaving the agent under-informed.

  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 60%, with since/until/from_user already described. The description adds general meaning by mapping keyword, language, dates, and author filter to the parameters, but does not provide deeper detail on format or constraints beyond that.

  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?

  Description clearly states a search over recent posts with keyword and optional filters, giving a specific verb and resource. It does not explicitly distinguish itself from sibling tools like x_search, though 'recent' and the filter list help narrow 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: use this tool to search recent posts by keyword with optional language, date, and author filters. It does not explicitly state when to prefer this over x_search or x_search_status, nor does it mention any exclusions.

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

• fetch_tweetB
  3.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. 'Summarize details' is vague and doesn't specify what information is returned, whether it includes the full post content, or any rate limits or authentication requirements. This lack of detail leaves 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 sentence that is immediately informative and contains no filler. It is appropriately concise for the simple one-parameter 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?

  Given the lack of output schema and annotations, the description should explain what the 'summary' contains and what the output looks like. It does not, leaving the agent uncertain about the tool's return value and edge cases. The description is too minimal to be considered complete.

  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 only a 'url' parameter with no description. The tool description clarifies that this URL is an X post URL, adding some meaning. However, it doesn't specify the expected format (e.g., full URL versus ID) or validate the input, so it only partially compensates for the 0% schema description 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 uses a specific verb ('Fetch and summarize') and clearly identifies the resource ('one X post URL'). It distinguishes from sibling tools like search_tweets and get_trends by focusing on a single URL rather than searches or trends.

  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 phrase 'for one X post URL' implies that this tool is used when you already have a specific post URL, as opposed to searching for posts. However, it does not explicitly mention alternatives or state when not to use it, so the guidance is implied rather than explicit.

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

• x_search_statusA
  4.2/5.0
  Behavior3/5

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

  No annotations are provided, so the description must convey behavior. It does disclose that no network call is made and implies a read-only check, which is useful. However, it does not describe what 'configuration' entails or what output/status info the tool returns.

  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 immediately conveys the core action and key constraint ('without making a network call'). No unnecessary 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?

  For a parameterless status/configuration check tool, the description provides the essential context: what it checks and that it is local. It lacks detail on the exact contents of the status or output format, but is largely complete for its simplicity.

  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 tool has zero parameters, so the baseline is 4. The description provides context about the tool's purpose ('configuration' check), which is sufficient given no parameters exist to explain.

  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 ('Check') and the resource ('x-search-plugin configuration'), and the explicit note 'without making a network call' distinguishes it from sibling tools that perform network-based searches or fetches.

  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 this tool is for local configuration checks, contrasting with network-dependent siblings. However, it does not explicitly state when to use it versus alternatives, nor provide direct exclusions, so it falls just short of full guidance.

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