Server Quality Checklist

Tool Scores

• extract_linksA
  4.3/5.0
  Behavior4/5

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

  Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds value by detailing the return structure (flags, anchor text, nofollow) and features like scope filtering and deduplication, enhancing the agent's understanding of behavior beyond the safe, read-only nature.

  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 three sentences long, with the core action in the first sentence and supporting details in the second. It is tightly written with no filler, effectively front-loading the most important information.

  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?

  The description covers the tool's purpose, output details, filtering capabilities, deduplication, limit, and use cases. With an output schema present and annotations providing safety context, the description is fully adequate for an agent to understand and invoke the tool 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 already documents each parameter's purpose. The description reiterates the overall functionality but does not add new semantic detail for individual parameters beyond what the schema provides, justifying a baseline score of 3.

  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 begins with 'List the links on a web page as absolute URLs' which is a specific verb and resource. It details the output (internal/external flags, anchor text, etc.) and distinguishes from siblings by mentioning link extraction specifically, not page contents or metadata.

  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 explicitly suggests use cases: 'crawling a documentation tree, auditing outbound links or finding next pages.' This provides clear context for when to use the tool, but does not include exclusions or alternatives, which would push it to a 5.

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

• extract_metadataA
  4.3/5.0
  Behavior4/5

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

  The description adds value beyond annotations by stating the tool avoids fetching the page twice, implying efficiency. It also discloses the breadth of metadata extracted (e.g., JSON-LD, RSS feeds, hreflang). No contradiction with annotations (readOnlyHint, idempotentHint, etc.).

  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 well-structured sentences: the first lists all extracted metadata types, the second provides usage guidance. No fluff, every phrase adds value. Front-loaded with key information.

  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 complexity (5 parameters, sibling tools), the description is complete. It covers purpose, usage, output scope, and efficiency benefits. The presence of an output schema means return values need no further explanation.

  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 coverage is 100%, so baseline is 3. The description does not add parameter-level details beyond the schema, but the schema descriptions are self-explanatory (url, timeoutMs, booleans). No extra semantic value from description.

  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: extracting structured metadata from a web page without downloading it twice. It lists 12 specific metadata elements (title, meta description, etc.), which distinguishes it from sibling tools fetch_page_markdown and extract_links.

  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 explicitly advises using this tool 'to classify or summarise a page cheaply before fetching its full text,' providing clear context for when to use it. It does not mention when not to use it or name alternatives, but the guidance is sufficient.

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

• fetch_page_markdownA
  4.7/5.0
  Behavior5/5

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

  Annotations already declare readOnly, openWorld, idempotent, non-destructive. Description adds specific behaviors: removes scripts, styles, ads, navigation chrome (by default), resolves relative links, keeps tables/code blocks/lists, and paginates. No contradiction.

  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?

  Three sentences, each serving a distinct purpose: purpose, behavior details, pagination instructions. Front-loaded and no redundant information.

  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 number of parameters, annotations, and presence of output schema, the description covers all key behaviors (what is stripped, pagination, link/image handling) without gaps. No missing critical information.

  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?

  Schema description coverage is 100%, but the description adds context beyond schema (e.g., pagination mechanism, default behavior for mainContentOnly). This extra value justifies above baseline 3.

  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 verb (Fetch, convert) and resource (web page, Markdown) with a specific purpose (reading or analysis). It implicitly distinguishes from siblings extract_metadata and extract_links by focusing on full-page conversion to Markdown.

  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?

  Provides explicit guidance on pagination ('when truncated is true, call again with startIndex: nextStartIndex') and mentions defaults. However, does not explicitly state when not to use this tool versus siblings.

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