Server Quality Checklist

Tool Scores

• bocha_web_searchA
  3.6/5.0
  Behavior3/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 discloses the output content and available formats (Markdown vs raw JSON), which adds behavioral context. However, it omits details like rate limits, result ordering, error behavior, or authentication requirements, leaving notable gaps.

  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 sentence that front-loads the core purpose and then lists useful output details. It is succinct and avoids fluff, though it could be split into two sentences for better readability. Still efficient for the information conveyed.

  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?

  With no output schema and no annotations, the description must explain what the tool returns; it does enumerate result fields and output formats. However, it lacks information about result ordering, pagination, error handling, or any prerequisites, leaving the tool 'usable but not fully specified' for complex decisions.

  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 input schema covers all five parameters with descriptions (100% coverage). The description adds no extra meaning beyond the schema, merely referencing the output format options already documented. Baseline 3 is appropriate given the schema's completeness.

  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 performs web search using Bocha AI and specifies the exact result fields (title, URL, snippet, site name, icon, publish time). It uses a specific verb+resource combination, making the tool's function unmistakable even without sibling differentiation.

  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 web search needs but provides no explicit guidance on when to use this tool over alternatives or when not to use it. Since no alternatives are mentioned, the context is clear enough for a basic search tool, but exclusions and prerequisites are absent.

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