Server Quality Checklist

Tool Scores

• websearch_searchA
  3.6/5.0
  Behavior3/5

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

  Annotations already cover key traits (read-only, non-destructive, idempotent, open-world). The description adds context about using DuckDuckGo and markdown output format, which is useful but doesn't disclose rate limits, authentication needs, or error behaviors beyond annotations.

  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, efficient sentence with zero waste—front-loaded with the core action and output. Every word earns its place, making it highly concise and well-structured.

  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, rich annotations, and the presence of an output schema, the description is reasonably complete. It covers the purpose and output format, though it could benefit from more explicit sibling differentiation or behavioral details like rate limits.

  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 parameters are fully documented in the schema. The description does not add any semantic details beyond what the schema provides (e.g., query purpose, result limits, region codes). Baseline 3 is appropriate.

  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 action ('Search the web') and the resource (web content via DuckDuckGo), with a specific output format ('return results as a markdown list'). It distinguishes from siblings by focusing on search-only functionality without fetching pages, though not explicitly named.

  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 searches with markdown output, but does not explicitly state when to use this tool versus alternatives like 'websearch_fetch_page' or 'websearch_search_and_fetch'. No exclusions or prerequisites are mentioned.

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

• websearch_fetch_pageA
  4.1/5.0
  Behavior4/5

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

  Annotations already indicate read-only, non-destructive, idempotent, and open-world behavior. The description adds valuable context beyond annotations by specifying the conversion method ('html-to-markdown'), performance aspect ('high-performance'), and token usage reduction, which helps the agent understand practical implications. No contradiction with annotations.

  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 purpose and followed by implementation details and benefits. Every sentence adds value: the first defines the tool's function, and the second explains the conversion method and efficiency gains, with no wasted words.

  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 the tool's moderate complexity, rich annotations (covering safety and behavior), and the presence of an output schema (which handles return values), the description is complete enough. It covers the purpose, method, and key benefits, leaving structured fields to detail parameters and outputs, making it well-rounded for agent use.

  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 fully documents all parameters. The description does not add any parameter-specific details beyond what the schema provides, such as explaining URL validation or metadata content. It only mentions the overall output format ('clean markdown'), which aligns with the baseline for high schema 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 clearly states the specific action ('fetch a URL'), resource ('its content'), and transformation ('as clean markdown'), distinguishing it from siblings like websearch_search (which likely returns search results) and websearch_search_and_fetch (which combines search and fetch). It explicitly mentions the conversion method ('html-to-markdown') and benefit ('dramatically reduces token usage').

  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 by stating it fetches a URL and converts to markdown, but it does not explicitly say when to use this tool versus alternatives like websearch_search_and_fetch. It mentions the benefit of reduced token usage, which provides some context, but lacks clear guidance on prerequisites or exclusions.

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

• websearch_search_and_fetchA
  4.5/5.0
  Behavior4/5

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

  Annotations cover safety (readOnlyHint: true, destructiveHint: false) and idempotency (idempotentHint: false), but the description adds useful context about efficiency and the combined operation. It doesn't contradict annotations and provides additional behavioral insight, though it could 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?

  The description is concise and front-loaded, consisting of two sentences that efficiently convey the tool's purpose and usage without unnecessary details. Every sentence adds value, making it well-structured.

  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 the tool's moderate complexity, rich annotations (including readOnlyHint, destructiveHint, idempotentHint, openWorldHint), and the presence of an output schema, the description is complete enough. It covers purpose, efficiency, and differentiation from siblings, which is sufficient for an agent to use it correctly.

  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 fully documents parameters. The description mentions 'top result pages' and 'fetch as markdown,' which adds some context beyond the schema, but doesn't provide detailed semantics. Baseline 3 is appropriate as the schema handles most parameter information.

  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's purpose with specific verbs ('search the web' and 'fetch top result pages as markdown') and distinguishes it from siblings by noting it 'combines search + fetch in one call for efficiency.' This explicitly differentiates it from websearch_search and websearch_fetch_page.

  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?

  The description provides explicit usage guidance by stating it's for efficiency when combining search and fetch operations, implying alternatives (using separate search and fetch tools) and when to use this tool (for combined operations). This helps the agent choose between this tool and its siblings.

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