Server Quality Checklist

Tool Scores

• fetchA
  4/5.0
  Behavior3/5

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

  Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful context about the operation being a full-page read beyond a preview, but does not disclose additional behavioral details such as output size, pagination, or error cases.

  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?

  A single, front-loaded sentence conveys purpose, source, and usage condition with no redundancy. Every word earns its place, and the condition ('when the preview is not enough') is placed at the end without obscuring the main action.

  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 tool is simple: one required parameter, clear schema coverage, and annotations that establish safety. The description explains when to use it and what it opens, and the output schema exists to define return values. It is complete enough, though it could slightly strengthen guidance on the expected context after a search result.

  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 input schema has 100% description coverage: the only parameter 'id' is clearly described as an 'Exact Subject or Observation ID returned by a Pod search result.' The main description reinforces this by linking it to a Pod search result, but adds little beyond what the schema already provides.

  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 ('Open') and names the resource ('complete review or subject page'), sourced from a Pod search result. It clearly distinguishes this from siblings like 'search' and 'inspect_mcp' by focusing on opening the full page rather than searching or previewing.

  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 states a clear trigger condition: 'when the preview is not enough.' It implies the tool is used after a Pod search result, but it does not explicitly mention when not to use it or name alternatives, so it falls short of full usage routing.

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

• searchA
  4.1/5.0
  Behavior4/5

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

  The annotations already establish read-only, idempotent, non-destructive behavior, and the description adds a useful behavioral constraint: anonymous searches return at most five results. This goes beyond the annotations and helps set expectations about output volume. There is no contradiction between the description and 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 three tight sentences, each earning its place: purpose, when to use, and a behavioral limitation. It is front-loaded with the core action and contains no filler or redundant phrasing.

  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?

  For a simple read-only search tool with a fully documented input schema, optional parameters, rich annotations, and an output schema, the description covers the essential operational context: what to search, when to use it, and the anonymous result cap. No critical detail needed for correct invocation is missing.

  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%, and each of the four parameters already has its own descriptive text, so the description does not need to restate parameter meaning. The description's anonymous-result note complements the limit parameter at a behavioral level rather than adding parameter-level semantics. This matches the baseline for high schema coverage.

  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 a specific action and resource: searching what people and agents actually experienced with products, APIs, services, places, or organizations. This aligns well with the title 'Search reviews' and makes the tool's purpose unambiguous. However, it does not explicitly differentiate itself from sibling tools like find_mcp or inspect_mcp.

  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 explicit timing guidance: use this before choosing, buying, integrating, visiting, or recommending something. This is clear contextual direction for an agent. It does not, however, mention when not to use it or name alternative sibling tools.

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

• feedbackA
  4.2/5.0
  Behavior4/5

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

  Annotations already indicate this is not read-only and not destructive. The description adds useful behavioral context: feedback is private, does not send a message or publish content, and works without sign-in. This goes beyond what annotations provide without contradicting them.

  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 sentences, no filler. The core purpose is front-loaded, followed by two brief clarifications that each add decision-relevant value: no message/publish behavior and no sign-in requirement.

  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 rich schema and output schema presence, the description covers selection and side-effect expectations well. It could slightly improve by framing when in the workflow to call it, but the available context is sufficient for a straightforward feedback-recording tool.

  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 every parameter's meaning is already documented. The description reinforces the helpful/improvement framing for 'kind' and 'message', but does not add new parameter-level semantics beyond the schema, consistent with the baseline for full 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 names a specific action ('Record') and a clear resource ('private product feedback inside Pod'), and explains what the feedback captures ('whether results helped or what capability was missing'). It also explicitly distinguishes this from messaging or publishing, which prevents confusion with content-sharing tools.

  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 makes it clear this is for recording feedback about Pod's usefulness, not for communicating or publishing. It does not explicitly name sibling alternatives or state 'use this when...', but the positive and negative scope is strong enough for an agent to route correctly.

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

• find_mcpA
  4.3/5.0
  Behavior4/5

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

  Annotations already mark this as read-only and idempotent; the description adds meaningful behavioral expectations: results are compact, directory provenance is kept separate from compatibility, and observed capabilities are kept separate from upstream claims. It does not discuss pagination or default behavior, but the output schema and annotations reduce the risk.

  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 sentences with no fluff: the first states the resource and search dimensions, the second sets result expectations and names the sibling for deeper evidence. Key differentiators are front-loaded.

  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 100% parameter schema coverage, an output schema, and read-only/idempotent annotations, the description covers what an agent needs to select and invoke the tool correctly. It also clarifies the follow-up path to inspect_mcp.

  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?

  Input schema already describes every parameter (100% coverage), so the description need not repeat syntax. It adds useful conceptual grouping—claimed/observed capability, provenance vs compatibility—but does not materially expand individual parameter meaning beyond the schema.

  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 ('Find') and a specific resource ('canonical MCP servers'), then lists search dimensions that distinguish it from generic search. It also differentiates from inspect_mcp by noting it returns compact directory results rather than full evidence.

  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 routes to inspect_mcp when full evidence is needed, which clarifies the main alternative. It does not discuss relative use of search/fetch/feedback, but the primary decision is covered.

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

• inspect_mcpA
  4.3/5.0
  Behavior4/5

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

  Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds meaningful behavioral context by disclosing that GitHub reports remain separate from firsthand Pod observations, indicating how data sources are kept distinct and how the tool treats provenance.

  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 with no filler. The core action and source are front-loaded, and the second sentence adds an important provenance distinction without redundancy.

  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 read-only nature, full parameter schema, rich annotations, and presence of an output schema, the description is complete enough for correct invocation. It states the required input source, the content that will be inspected, and the separation of data provenance.

  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 input schema already provides 100% coverage for all three parameters, including the UUID constraint for id, the ranking/filtering purpose of query, and the 1–20 range for issueLimit. The description adds no parameter-specific detail beyond what the schema already states, 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 uses a specific verb ('Inspect') with a clear resource ('one canonical MCP from find_mcp') and enumerates the exact content returned: upstream claims, deployments, Pod-observed tools, and decision-useful GitHub issues. This makes it easily distinguishable from find_mcp and the other sibling tools.

  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?

  It clearly implies the workflow: first use find_mcp to obtain a canonical MCP ID, then inspect that server. It does not explicitly name alternatives or say when not to use the tool, but the 'from find_mcp' context is strong enough for an agent to infer the right situation.

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