Server Quality Checklist

Tool Scores

• web_url_readA
  3.6/5.0
  Behavior3/5

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

  The description states a read operation, consistent with the readOnlyHint annotation, and adds that it returns content from a URL. However, it provides no additional behavioral details beyond what annotations already imply, such as output format or handling of dynamic content.

  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 short and front-loaded with the core purpose. The second sentence is somewhat redundant and awkwardly phrased ('further information retrieving'), but it does add a usage hint without being verbose.

  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 the tool has six parameters including section, readHeadings, and paragraphRange, the description only says 'Read the content' without explaining how output varies with these options. The schema describes parameters well, but the absence of an output schema and limited description leaves some ambiguity about return behavior.

  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 all six parameters. The description adds no parameter-specific meaning, keeping this at the baseline.

  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 reads content from a URL with a specific verb and resource. It is distinguishable from the sibling search tool, though it doesn't explicitly differentiate itself.

  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?

  'Use this for further information retrieving to understand the content of each URL' provides a clear intended use case as a follow-up to retrieving URLs. It lacks explicit exclusions or alternative guidance, but the sibling name makes the contrast evident.

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

• searxng_web_searchA
  4/5.0
  Behavior3/5

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

  Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds that it uses the SearXNG API but no further behavioral details like pagination, result limits, or output format. This is adequate but not rich, consistent with the caliber where annotations carry most load.

  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-loaded with the core action and then followed by use cases. Every sentence earns its place, with zero wasted words or redundancy.

  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 tool's moderate complexity (5 params, 2 enums) and lack of output schema, the description provides sufficient context for typical use cases, covering the intent and scope. It doesn't explain return values, but the readOnly hint and param names compensate. A small gap in behavioral details (e.g., pagination) prevents a 5.

  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 all 5 parameters (query, pageno, language, safesearch, time_range) are already documented in the schema with descriptions. The description adds no extra parameter meaning beyond what the schema provides, so the baseline of 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 tool 'performs a web search using the SearXNG API', identifying both the action and resource. It distinguishes itself from the sibling web_url_read by focusing on broad queries rather than reading a specific URL, making it unambiguous.

  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 provides clear usage context: 'ideal for general queries, news, articles, and online content' and 'Use this for broad information gathering, recent events, or when you need diverse web sources.' It implies when to use but does not explicitly state when not to use it or mention alternatives beyond the sibling, which keeps it just under a 5.

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