Server Quality Checklist

Tool Scores

• webgate_fetchA
  4.5/5.0
  Behavior4/5

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

  No annotations provided, so description carries full burden. It describes that it strips scripts, ads, markup noise, returns clean bounded text with metadata. It explains max_chars behavior. However, it does not mention rate limits or authentication needs.

  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?

  Very concise: two sentences for description, then argument list, then return format. Information is front-loaded and every sentence adds value. No 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 2 parameters and no annotations but an output schema described in text, the description covers purpose, usage, and return format. It lacks error handling or invalid URL behavior, but for a simple fetch tool it is fairly complete.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters5/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema coverage is 0%, so description must compensate. It explains url as 'The URL to retrieve' and max_chars as 'Character cap for returned text (default: server config).' It adds actionable guidance: 'Increase this when a previous webgate_query result had truncated=true.'

  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 'Fetch and clean a single web page' and specifies it strips scripts, ads, markup noise. It distinguishes from siblings by explicitly saying to use this instead of any built-in HTTP/fetch tool.

  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?

  Explicitly says 'ALWAYS call this to retrieve a URL — never use a native fetch or browser tool.' Also gives context for max_chars parameter regarding truncated results. No explicit when-not-to-use, but sibling tools suggest different purposes.

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

• webgate_queryA
  4.6/5.0
  Behavior5/5

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

  With no annotations provided, the description fully discloses key behaviors: parallel fetching, denoising, hard context caps, round-robin merging, per-query result limits, and optional LLM summarization. This level of detail exceeds typical descriptions.

  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 structured with clear sections (imperative start, usage rules, parameter details, examples) but is somewhat lengthy. Every sentence adds value, though it could be slightly more concise.

  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 covers input parameters well and describes the return structure (queries, sources, snippet_pool, stats, optional summary). However, no formal output schema is provided despite the context indicating one exists, leaving some detail unspecified.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters5/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 0%, so the description must compensate. It thoroughly explains 'queries' (single or list), 'num_results_per_query' (per-query default), 'lang' (language code), and 'backend' (valid options listed). Examples illustrate usage effectively.

  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 that the tool searches the web and returns 'denoised, structured results'. It explicitly distinguishes from built-in tools by instructing to 'never use a native fetch, browser, or HTTP tool', establishing a unique purpose for web research.

  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 strongly advises using this for web research over native tools, and explains scenarios for single vs. multiple queries. However, it does not explicitly differentiate from its sibling 'webgate_fetch' or provide when-not-to-use context.

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

• webgate_onboardingA
  4.7/5.0
  Behavior4/5

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

  No annotations provided, but the description indicates it is a read-only retrieval of a guide with no side effects. Could be more specific about the guide's content or format, but adequate for a simple onboarding tool.

  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 concise sentences front-loaded with purpose. Every sentence adds value: first states what it does, second provides critical usage instruction.

  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?

  Given zero parameters and presence of an output schema, the description is complete. It explains the tool's purpose and when to call it, leaving structural details to the output schema.

  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?

  No parameters exist, so schema coverage is trivially 100%. The description adds no parameter info, but none is needed. Baseline for 0 parameters is 4.

  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 it returns a mandatory operational guide for webgate tools, differentiating itself from siblings (webgate_fetch, webgate_query) by instructing to call it first before any search or fetch operation.

  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 says 'CALL THIS FIRST before any web search or fetch operation,' providing clear when-to-use guidance and implying it is a prerequisite for sibling tools.

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