Server Quality Checklist

Tool Scores

• x_searchA
  3.9/5.0
  Behavior3/5

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

  No annotations are provided, so the description bears full responsibility. It discloses that media understanding may increase latency, date format is YYYY-MM-DD, and that allow and exclude filters cannot be combined with a max of 10 handles each. However, it does not describe return behavior, pagination, authentication needs, or other effects, leaving 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 extremely concise with 4 sentences, no redundancy. The first sentence states the core purpose, the second provides usage guidance, the third lists constraints, and the fourth mentions a behavioral note. Every sentence adds value.

  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, no output schema, and no annotations, the description addresses key constraints and usage context but lacks details on pagination, result format, error handling, and rate limits. It is adequate but not fully comprehensive.

  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 0%, so the description must provide parameter meaning. It explains the constraints on allowed/excluded handles (max 10, cannot combine) and date format, and mentions latency impacts of media understanding. However, it does not individually explain all 7 parameters, leaving some underspecified.

  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 'Search current X posts, profiles, and threads using xAI's X Search.' It uses a specific verb ('search'), identifies the resource (X posts, profiles, threads), and indicates the scope ('current'). It distinguishes from general web search, providing purpose clarity.

  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 advises using this tool for 'current discussion or claims on X' and explicitly mentions constraints like handle filter limits and date format. It implies an alternative (general web search) but does not explicitly state when not to use or list other alternatives beyond that single mention.

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