Server Quality Checklist

Tool Scores

• lookup_codeB
  3.1/5.0
  Behavior3/5

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

  Annotations already declare readOnlyHint=true and openWorldHint=true, indicating safe read-only operation with a known set of codes. The description adds no extra behavioral context beyond 'resolves to official description', which is consistent but not additional.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness3/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single sentence with no wasted words, but it is under-specified rather than efficiently complete. It is concise but sacrifices necessary detail.

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

  Completeness2/5

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

  Given three parameters (two required, with enums) and an output schema, the description lacks context about code format, case sensitivity, or the nature of the official description. The output schema is not shown, but even with it, the description should provide usage context.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters2/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 0%, so the description must compensate. It mentions 'CPV or NUTS code' hinting at the 'list' and 'code' parameters, but does not explain the 'language' parameter or the expected format of the code. This is insufficient for three parameters with no schema descriptions.

  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 clearly states the verb 'resolves' and the resource 'CPV or NUTS code' to its 'official description'. It is distinct from siblings like 'search_tenders' which deal with tenders, not code resolution.

  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?

  No guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The description only states what it does, not when or why to invoke it.

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

• get_export_urlA
  3.8/5.0
  Behavior4/5

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

  Annotations already provide readOnlyHint and openWorldHint. The description adds actionable advice: 'download it outside this server' due to the large ZIP size. This enhances transparency beyond the annotations, though it could mention rate limits or authentication requirements.

  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 consists of two efficient sentences: the first states the core purpose, and the second provides a critical behavioral caveat. No redundant information, every word earns its place.

  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 description covers the main purpose and a key usage note. However, it is missing clarity on whether 'day' and 'month' are mutually exclusive or what happens when both are omitted (all parameters optional). Output schema may fill gaps, but a small clarification would make the description fully self-contained.

  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 high (67%), with clear format descriptions for 'day' and 'month' and an enum for 'format'. The tool description adds no further parameter meaning beyond what the schema already provides, so the baseline score of 3 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 clearly states the verb ('Builds the URL') and the resource ('official bulk export for one day or month'). It distinguishes the tool from sibling tools like 'search_tenders' and 'get_tender' by focusing on bulk export URL generation.

  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 does not provide any guidance on when to use this tool versus alternatives or how to choose between the 'day' and 'month' parameters. It only mentions a precondition ('must already be closed') without explaining the use case for each parameter option.

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

• get_tenderA
  4.2/5.0
  Behavior4/5

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

  Annotations already provide readOnlyHint and openWorldHint, correctly indicating no side effects and external data mutability. The description adds value by detailing the behavioral difference between formats: summary is a curated extraction, while other formats are returned verbatim. This goes beyond what annotations offer.

  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: the first states the core purpose, the second explains the critical format differentiation. No redundant information; every sentence earns its place. Highly front-loaded and efficient.

  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 has few parameters (all described in schema), an output schema, and comprehensive annotations, the description covers the essential behavioral nuance of formats. It could mention the default version behavior or error handling, but the agent has sufficient information for correct 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 description coverage is 100%, so baseline is 3. The description adds meaningful context for the 'format' parameter by explaining what 'summary' extracts (deadlines, lot values, suitableFor, document links) and that other formats are verbatim. This enhances agent understanding beyond the schema's enum descriptions.

  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 it fetches a single notice, uses a specific verb ('fetches'), and explains the key distinction between the 'summary' format (curated extraction of bidder-relevant fields) and other verbatim formats. This effectively distinguishes it from sibling search tools.

  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?

  While the description implies the tool is for retrieving a single notice after obtaining an ID from a search, it does not explicitly state when to use it versus alternatives like search_tenders. No exclusion criteria or alternative tools are mentioned, leaving the agent to infer usage context.

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

• search_tendersA
  4.5/5.0
  Behavior4/5

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

  Annotations already provide readOnlyHint and openWorldHint. Description adds default filtering and sorting behavior, as well as the specific website. No contradictions. Adds useful context beyond 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?

  Two sentences, front-loaded with core action and defaults. Second sentence provides key alternative. No wasted words.

  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 19 optional parameters, an output schema that documents return values, and a sibling tool reference, the description is sufficiently complete. It covers the tool's purpose, defaults, and when to use an alternative.

  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 74%, so the schema already documents most parameters. The description mentions defaults for onlyActive, noticeTypes, and sort, but these are already in the schema. No new parameter semantics beyond what schema 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?

  Specifically states it searches lots on oeffentlichevergabe.de with defaults (open lots, competition notice types, newest first). Clearly distinguishes from sibling search_tenders_raw by saying 'use for anything this does not cover'.

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

  Usage Guidelines5/5

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

  Explicitly provides default behavior and references an alternative tool for cases not covered. This gives clear when-to-use guidance.

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

• search_tenders_rawA
  4.7/5.0
  Behavior5/5

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

  Annotations declare readOnlyHint=true and openWorldHint=true. The description aligns: it describes a read operation ('posts a query ... unchanged') and adds behavioral nuances not covered by annotations, such as: 'RANGE_DAYS n means field >= midnight Europe/Berlin of today + n days, not a window', 'Other fields answer HTTP 500' for ORDER, and operator operand constraints. 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.

  Conciseness4/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single dense paragraph. It front-loads the core action and then dumps operators and fields. While every sentence adds value, the lack of bullet points or breaks may hinder quick scanning. However, it is not verbose and efficiently packs necessary information. Could be slightly more structured but still effective.

  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 5 parameters (0 required), nested objects, an output schema, and high complexity, the description covers query structure, operator semantics, field lists, FROM variations, ORDER limitations, and provides a reference to a full contract. It addresses pagination implicitly via PAGE parameter, and mentions error behavior for ORDER. No major gaps for a power-user tool.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters5/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema coverage is 60%, but the description adds substantial meaning beyond the input schema. It enumerates all operators with their operand requirements (e.g., 'Text and temporal operators take exactly one operand; IN and STARTS_WITH OR a list'), lists all field names on lots with examples (e.g., 'estimatedValue (''150000 EUR'')'), and clarifies constraints like RANGE_DAYS behavior. This compensates for schema gaps and aids correct parameter construction.

  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 action: 'Posts a WHERE/FROM/PAGE/ORDER query to /bkmk/searches unchanged.' It names the HTTP method (POST), the endpoint, the query structure, and lists operators and fields. This clearly distinguishes it from the sibling 'search_tenders' tool, which likely provides a simpler search interface.

  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 provides extensive operator and field listings, guiding the agent on how to construct queries. It also notes that the 'notices' FROM value has a smaller field set. However, it does not explicitly compare with the sibling 'search_tenders' to state when to use this raw DSL version versus a simpler alternative. Missing explicit when-not or alternatives, but the detail implies usage for complex filtering.

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