Server Quality Checklist

Tool Scores

• backlink_profileA
  3.5/5.0
  Behavior3/5

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

  No annotations are provided, so the description carries the full burden. The verb 'Get' implies a read-only operation, and the price is disclosed. However, there is no explicit statement that the tool does not modify anything, nor any mention of rate limits or authentication requirements. For a simple lookup tool, the read-only nature is reasonably implied, but not fully explicit.

  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: a concise summary up front, followed by pricing and a bulleted list of returns. It is not overly verbose, and the key purpose is front-loaded. The only minor detraction is the pricing line, which is not directly about tool behavior but still useful.

  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?

  For a tool with a single parameter and no output schema, the description is fairly complete: it lists the specific metrics returned and mentions pricing. It does not explain the exact format of the 'domain' input beyond the schema example, but that is adequate. The tool is simple enough that no further context is required.

  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?

  The schema describes the single 'domain' parameter with an example, and the description repeats it without adding new meaning. Schema coverage is 100%, so the baseline of 3 is appropriate; the description does not need to compensate for any gaps.

  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 states a specific verb ('Get') and resource ('backlink profile'), and clearly distinguishes its focus (referring domains, link metrics, anchor text) from sibling tools like on_page_audit and serp_analysis. It is immediately clear what this tool does and how it differs.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description provides no guidance on when to use this tool versus alternatives. It does not mention any specific conditions, prerequisites, or exclusions. The sibling tools are not referenced, leaving the agent to infer appropriate usage solely from the tool name and description.

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

• get_content_briefA
  3.7/5.0
  Behavior3/5

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

  With no annotations, the description carries the full burden for behavioral disclosure. It does disclose the price, the fact that it returns a detailed brief, and provides a bulleted list of output contents. However, it does not mention whether this is a paid/external API call with side effects, potential rate limits, or any authorization requirements. The output detail is helpful but incomplete for a paid tool.

  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 compact and front-loaded: it states the action and output type immediately, then gives a clear bulleted list of what the brief includes. The price line is useful context, though slightly detracts from the core flow. Overall every sentence earns its place despite minor formatting overhead.

  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 and no output schema, the description compensates well by enumerating the key sections of the returned brief. It omits error/edge-case behavior and does not mention language/location effects, but the essential information for calling the tool correctly (target keyword, output expectation, price) is present.

  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 fully documents all three parameters. The description adds no meaning beyond what the schema provides, aside from reinforcing that 'keyword' is the target. Baseline 3 is appropriate when the schema carries the parameter documentation burden.

  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 uses a specific verb ('Generate') and names a distinct resource ('POP content brief'), with the target keyword as the object. This clearly distinguishes it from siblings like backlink_profile or on_page_audit, none of which produce content briefs. It is unambiguous what this tool does.

  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 content brief creation but does not explicitly state when to prefer this over keyword_research or serp_analysis, nor does it mention any exclusions. The context is clear enough that an agent can infer the primary use case, but no direct comparative guidance is provided.

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

• keyword_researchA
  3.8/5.0
  Behavior3/5

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

  With no annotations, the description carries the full burden. It discloses that the tool costs $1.50 (x402 on Base), which is a behavioral trait beyond schema. However, it does not state whether it is a read-only operation, any rate limits, or potential errors. The cost is a useful addition, but other behavioral aspects are omitted.

  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 compact and well-structured: a single opening sentence stating the purpose, a price line, and a bulleted list of return values. It front-loads the core function and avoids any filler, making it easy to scan.

  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?

  For a tool with no output schema, the description adequately lists the return items. The parameter set is simple and fully described by the schema. The inclusion of pricing adds valuable context. Minor gaps, such as the format or type of the returned data, are acceptable given the tool's simplicity.

  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%, and all parameters have descriptions. The description adds no additional meaning beyond what the schema already provides; it merely repeats that 'keyword' is the target. For a tool with full schema coverage, this baseline 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 explicitly states the tool's function ('Research keyword metrics') and lists concrete outputs (search volume, CPC, competition, related suggestions). This clearly distinguishes it from sibling tools like backlink_profile or on_page_audit, which have different focuses.

  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?

  Usage context is implied by the purpose, but the description provides no explicit guidance on when to choose this tool over alternatives. It does not mention any conditions, exclusions, or sibling comparisons. The agent must infer that keyword metrics are needed.

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

• serp_analysisA
  3.8/5.0
  Behavior4/5

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

  With no annotations provided, the description carries the full burden, and it does disclose the key behavioral facts: it returns exactly ten organic results with authority metrics, snippets, and SERP feature detection, and it costs a listed price. It does not mention rate limits or authentication, but for a read-style analysis tool the return contract is otherwise explicit.

  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 compact and front-loaded with the core action, followed by cost and a bulleted return list. Every sentence earns its place, and the structure makes the return contract easy to scan. The only mildly cryptic element is 'x402 on Base,' but it does not hurt readability.

  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?

  For a low-complexity tool with one required parameter, the description provides enough to invoke it: the required keyword, cost, and a detailed list of return values. It could add explicit notes on how language and location affect results or describe the exact response format, but with no output schema the Returns list largely covers an agent's needs.

  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%, since keyword, language, and location each have explicit descriptions in the input schema. The tool description itself adds no extra meaning about how language or location affect the analysis, so it stays at the baseline 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 opening line names a specific action ('Analyze the top 10 SERP results') and a concrete resource ('for a keyword with metrics'), so an agent can immediately identify this as the SERP-analysis tool rather than a generic keyword tool. The bulleted return list further pinpoints the tool's scope, distinguishing it from siblings like keyword_research and backlink_profile.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description never says when to choose serp_analysis over keyword_research, on_page_audit, or backlink_profile. There is no 'use when...' or 'instead of...' guidance; the closest is the implication in the first line, which is not an explicit routing rule.

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

• on_page_auditA
  3.9/5.0
  Behavior3/5

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

  With no annotations, the description must carry the behavioral burden, and it does disclose the $2.50 price and the outputs. Yet it does not clarify what 'x402 on Base' means, whether the URL is fetched live, or any limitations or error behavior, leaving meaningful behavioral gaps.

  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 purpose is front-loaded in one sentence and the returns are formatted as scannable bullets with no filler. A small deduction is taken for the cryptic 'x402 on Base' phrase, which is not explained and may confuse an agent.

  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?

  For a one-parameter tool with no output schema, the description supplies the essential context: what the audit checks, what it returns, and what it costs. It does not detail response formatting or error behavior, but those are minor gaps given the return list.

  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%, and the single url parameter is already described in the input schema. The description adds no additional parameter-level semantics, so the baseline of 3 applies.

  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 opens with a specific verb and resource: 'Run a comprehensive on-page SEO audit for a URL.' This unambiguously states the tool's function and, through the on-page framing, separates it from sibling tools such as keyword_research or serp_analysis.

  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 context that this tool is for auditing a URL's on-page SEO elements, and the returns list signals the kinds of issues it addresses. However, it never explicitly names alternatives or states when not to use this tool, so it falls just short of fully explicit routing.

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