Server Quality Checklist

Tool Scores

• search_webA
  4.2/5.0
  Behavior3/5

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

  No annotations provided, so description bears full burden. It describes the main behavior (search and convert to markdown) and return format, but does not disclose potential limitations like rate limiting, error handling, or result filtering details.

  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 well-structured with a clear action sentence followed by detailed Args/Returns. It is slightly verbose but every sentence adds value. Front-loaded with purpose, then parameter details.

  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 simplicity (3 parameters, no nested objects), the description is sufficiently complete. It covers the return format, though the actual output schema is not in the prompt. Sibling tools provide context for selection.

  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%, but the description adds full semantic meaning for all parameters: q is 'free text', k is 'how many results (1-10, default 5)', max_tokens is 'optional per-result soft cap'. This fully compensates for missing schema descriptions.

  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 explicitly states 'Run a web search and return the top-k result pages already converted to clean Markdown', providing a specific verb and resource. It distinguishes itself from sibling tools (fetch_page, fetch_pages_batch) by noting that it combines search and read in one call.

  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 gives clear guidance: 'Use this whenever you need fresh information from the public web'. It implies that siblings are for fetching known URLs, but does not explicitly state when not to use this tool.

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

• fetch_pageA
  4.3/5.0
  Behavior4/5

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

  No annotations exist, so the description carries full burden. It discloses truncation behavior with max_tokens, return format (clean Markdown), and purpose. Missing error handling details, but core behavior is clear.

  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: a single sentence plus clean Args and Returns sections. No fluff, every sentence adds value.

  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 presence of an output schema and sibling tools, the description provides enough context for typical use. Could mention error scenarios, but overall it's adequate for a single-page fetch tool.

  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 fully compensates by explaining url as fully-qualified http(s) URL and max_tokens as soft cap with truncation marker. Adds critical context beyond the schema types.

  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 it fetches a single web page or PDF and returns clean Markdown. It contrasts with sibling tools: 'single' vs batch, and URL-based vs search, providing clear 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 use when you have a specific URL, but lacks explicit guidance on when to prefer this over fetch_pages_batch or search_web. No when-not or alternative scenarios are mentioned.

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

• fetch_pages_batchA
  4.7/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 declares concurrency (parallel), input limits (up to 25 URLs), per-URL soft cap (max_tokens), and output structure (ordered list with success/error). Missing: rate limits, auth, retries, timeouts. But for a batch fetch, these are sufficient to inform the agent.

  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?

  Description is compact (~6 lines), with clear Args and Returns sections. No redundant or irrelevant information. Every sentence adds value.

  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?

  Output schema exists (signal true), so return values are explained in description. Inputs fully described. Completeness is high for a straightforward batch fetch tool; minor omission: no explanation of potential error types or edge cases like invalid URLs.

  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 'urls: Up to 25 URLs' and 'max_tokens: Optional per-URL soft cap on the returned Markdown.' This adds crucial constraints and semantics beyond the schema types.

  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 'Fetch many web pages in parallel and return each one's clean Markdown.' It distinguishes from sibling tools: fetch_page (single page) and search_web (search). The verb 'fetch' and resource 'web pages' are specific, and the batch aspect is highlighted.

  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?

  Explicit guidance: 'Use this whenever you need to read more than one URL at once — it is far faster than calling fetch_page in a loop.' This directly tells when to use and why, contrasting with the sibling fetch_page.

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