Server Quality Checklist

Tool Scores

• search_docsB
  3.4/5.0
  Behavior3/5

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

  Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, covering safety and repeatability. The description adds that the search operates over 'indexed' documentation and returns only paths and titles, which is useful but does not go beyond what the annotations and output schema already convey. No contradictions.

  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 a single, front-loaded sentence that names the action, the resource, and the result shape with no wasted words. It is appropriately sized for the tool's simplicity.

  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 simple schema, full parameter descriptions, output schema presence, and annotations covering read-only/idempotent behavior, the description is largely sufficient for invoking the tool correctly. The main missing piece is sibling differentiation, which prevents a perfect score.

  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%, with both 'query' and 'limit' already documented in the input schema. The description adds no additional parameter-level meaning, so the baseline of 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 a specific action ('Search') and resource ('indexed GitLab documentation'), and specifies the return type ('matching paths and titles'). It does not explicitly contrast itself with siblings like get_doc or search_and_fetch, so it slightly falls short of full differentiation.

  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 implies when to use the tool (when searching docs is needed) but provides no guidance on when to prefer it over the sibling alternatives, nor any exclusion criteria. With siblings named get_doc and search_and_fetch, the absence of routing advice is a notable gap.

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

• search_and_fetchA
  4.1/5.0
  Behavior4/5

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

  Annotations already establish read-only and idempotent behavior, and the description adds useful context about the combined search-and-fetch outcome and that full markdown is returned for each hit. It does not discuss potential response size, but that is minor given the annotations and output schema.

  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?

  One sentence that front-loads the action and outcome with no filler. Every word contributes meaning.

  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 two-parameter tool with rich schema documentation, read-only/idempotent annotations, an output schema, and clear combined behavior, the description is complete. An agent has enough information to invoke it 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 fully documents query and limit. The description's phrase 'full markdown for each hit' slightly reinforces the limit's behavior, but it adds no new parameter-level 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?

  Description states a specific verb (search) and resource (documentation), and the key distinctive outcome: returns full markdown for each hit in one call. This directly differentiates it from siblings like search_docs or get_doc, which would require separate calls.

  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 phrase 'in one call' implies it should be used when both searching and retrieving full content are needed, but it does not explicitly name alternatives or state when not to use it. Usage context is inferred from the behavior rather than spelled out.

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

• get_docA
  4.3/5.0
  Behavior4/5

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

  Annotations already mark the tool as read-only and idempotent; the description adds that the response is the page's full Markdown content rather than a summary or search snippet. This clarifies output granularity and format beyond what the safety annotations convey.

  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?

  One sentence, front-loaded with the key action and resource, with no filler or redundant explanation. Every word contributes to selecting or invoking the tool.

  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 single-required-parameter read tool with an output schema and safety annotations, the description plus schema fully covers what an agent needs: what to fetch, how to identify the page, and that it is read-only/idempotent. No missing prerequisite or postcondition creates ambiguity.

  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 sole parameter, path, is already described as the exact document path from search results. The description only repeats 'by path' and does not add formatting, encoding, or alternate-source guidance, so it stays at the baseline for a fully documented 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?

  States a specific verb ('fetch'), resource ('full markdown content of a single documentation page'), and method ('by path'). This clearly distinguishes it from the search-oriented siblings search_docs and search_and_fetch, which find or combine docs rather than retrieving one known page.

  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 and path parameter make the usage context clear: call this when you already have the exact document path, which the schema says comes from search results. It does not explicitly name when-not-to-use conditions or alternatives, but the intended flow is easily inferred.

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