Server Quality Checklist

Tool Scores

• usePatternFlyDocsB
  3.2/5.0
  Behavior2/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. It discloses that the tool returns documentation and schemas and accepts up to 15 URIs, but it does not mention side effects, permissions, idempotency, or error behavior. For a retrieval tool, this is a noticeable gap in transparency.

  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 concise with a clear structure: a brief intro, a usage section (numbered steps), and a return section. It is easy to scan and contains no redundant information, though it could be slightly more streamlined.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness3/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool's simplicity and the fact that there is no output schema, the description covers the basic functionality and input options. However, it lacks details on error handling, what happens when a name or URI is invalid, and the exact format of the returned documentation. It is adequate but not comprehensive.

  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 each parameter is described in the schema. The description adds context by explaining the OR relationship between 'name' and 'urlList' and providing examples, which adds marginal value over the schema alone. 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 it retrieves markdown documentation and JSON schemas for PatternFly resources. The verb 'get' combined with the resource type conveys the purpose well, but it does not explicitly differentiate from the sibling tool 'searchPatternFlyDocs' in the description, though it hints at the relationship by mentioning typical input from search results.

  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 advises that input is typically from searchPatternFlyDocs results and provides options for input (name or URL list). However, it does not explicitly state when to use this tool vs. alternatives, nor does it mention when not to use it. The guidance is implied but not fully explicit.

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

• searchPatternFlyDocsA
  4.4/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 describes search behavior (case-insensitive, partial, wildcard) and return types. Implies read-only, non-destructive operation. Lack of explicit auth or rate limit info is acceptable for a search tool.

  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?

  Well-structured with clear sections for usage and returns. First sentence captures purpose. No wasted words; 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?

  No output schema, but description explains return values (bullet points). Parameters fully covered. Complexity moderate; workflow with sibling tool is explained. Complete enough for correct agent invocation.

  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 coverage is 100%, baseline 3. Description adds value by explaining wildcard support and version examples beyond schema descriptions. For searchQuery, it clarifies partial and full matches.

  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 searches PatternFly resources, returns component names with documentation URLs, and supports case-insensitive partial and wildcard matches. It distinguishes from sibling tool usePatternFlyDocs by explaining the workflow.

  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 usage steps: input a searchQuery, then use returned data with usePatternFlyDocs. Includes what is returned. No exclusion criteria or when-not-to-use mentioned, but the context is clear.

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