Server Quality Checklist

Tool Scores

• get_warningsB
  3.1/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 of behavioral disclosure. The description lists the returned fields but does not state whether the operation is read-only, whether data is cached or real-time, or any side effects. For a data-fetching tool, this is a notable gap.

  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, front-loaded sentence that begins with the core purpose and then lists relevant fields. It is concise and informative without being verbose, though the field list is somewhat long. Overall, it earns its place.

  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?

  There is no output schema, so the description must explain return values. It does list the key fields (e.g., nazwa_zdarzenia, stopien, prawdopodobienstwo), but it does not indicate the result structure (e.g., array of objects) or additional context like timezone or units. This is adequate but leaves some ambiguity.

  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?

  The input schema has zero parameters, so there is nothing to explain. Since the schema is empty, the baseline is 4 for parameter semantics. The description appropriately focuses on the output rather than parameters, which is correct for a no-parameter tool.

  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 verb ('Get') and resource ('active IMGW meteorological warnings across Poland'), and lists the returned fields. This makes the tool's purpose unambiguous and distinguishes it from weather/hydro siblings by focusing on warnings. However, it does not explicitly name an alternative, so it stops short of a perfect 5.

  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?

  There is no guidance on when to use this tool versus alternatives like get_weather or get_hydro. The description only states what it does, leaving the agent to infer its applicability. No exclusions or contexts are provided.

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

• list_hydro_stationsA
  3.8/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 of behavioral disclosure. It mentions the data source ('/hydro feed') and optional query filters, but does not state what happens when no filters are applied (e.g., returns all stations), rate limits, or pagination. For a simple list tool, this is adequate but lacks deeper transparency.

  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 concise sentences with no redundancy. The purpose and data source are front-loaded, followed by the filter note and the specific use case. 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?

  For a simple list tool with two optional filters and no output schema, the description provides sufficient information: what it lists, the source, and how it is used (for get_hydro). It does not describe the response format, but that is not critical for a list operation of this nature.

  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%, meaning both parameters (river, province) are already described in the schema. The description only says 'Optional query filters,' which adds no meaning beyond what the schema provides. 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 uses a specific verb ('List'), names the resource ('hydrological station names, rivers, and provinces'), and identifies the data source ('/hydro feed'). It also ties the tool to a downstream use case (finding the right station name for get_hydro), which differentiates it from siblings like list_weather_stations, though not explicitly.

  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 clearly states the primary context: 'Used to find the right station name for get_hydro.' It does not mention when not to use it or name alternative tools (e.g., list_weather_stations), but the intended usage is specific and actionable, satisfying the 'clear context' criterion.

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

• get_hydroA
  4/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 burden of behavioral disclosure. It transparently explains that the server computes an alarm_status field from current values vs. thresholds, which is not evident from the schema. This adds meaningful context about the tool's internal behavior, though it omits other traits like rate limits or error behavior.

  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 long, front-loads the core purpose, and lists key data fields without redundant detail. Every sentence contributes value, making it highly concise and well-structured.

  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 read-only tool with 5 optional parameters and 100% schema coverage, the description adequately conveys the data returned and the alarm_status behavior. The only minor gap is the absence of explicit guidance on pagination or handling of large result sets (though limit is in the schema), and it does not reference sibling tools for context, but overall it provides sufficient information for correct invocation.

  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 all parameters are fully documented in the input schema. The description does not add parameter-specific meaning beyond what the schema already provides, hitting 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 description clearly states the tool retrieves current hydrological readings from IMGW, enumerating specific fields (water level, flow rate, temperature, thresholds). This verb+resource definition is unambiguous and naturally distinguishes it from siblings like get_warnings (warnings vs. readings) and get_weather (weather vs. hydrology).

  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 hydrological data retrieval but does not explicitly state when to choose this tool over get_warnings or other siblings. There is no mention of alternatives or exclusions, leaving the agent to infer the appropriate context from the purpose alone.

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

• list_weather_stationsA
  4.2/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 burden. It discloses the data source ('/synop feed') but does not mention any behavioral traits such as read-only nature, ordering, pagination, or result format. The 'list' verb implicitly suggests read-only, but this is not 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?

  Two short sentences with no filler. The primary action is front-loaded, and the useful context about the feed appears immediately. Every word contributes 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?

  For a simple list tool with no parameters and no output schema, this description is largely complete. It states what it lists, from which feed, and why it's useful. It could optionally mention if the list is exhaustive or sorted, but that is not critical for basic 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?

  The tool has zero parameters, and the schema coverage is trivially 100%. The baseline for 0-parameter tools is 4, and the description doesn't need to add parameter details. It appropriately focuses on the output and use case.

  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 ('List') and resource ('synoptic station names'), and references the '/synop feed' for context. It clearly distinguishes this tool from siblings like list_hydro_stations by naming a different feed type.

  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 clear context: this tool is for finding the right station name, implying it is used as a precursor to other operations. However, it does not explicitly state when not to use it or name alternative tools.

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

• get_weatherA
  4.3/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 of behavioral disclosure. It credibly reveals data update frequency (~hourly), the scope behavior with and without station, and enumerates the returned fields with units. Missing minor details like error conditions or aggregation behavior, but for a read-only weather observation tool this is solid forward disclosure.

  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?

  Four front-loaded sentences with zero wasted words. Purpose leads, followed by scope behavior, freshness, and return fields. The field list earns its place as a substitute for an output schema. Every sentence delivers new, non-redundant information beyond what annotations or schema already provide.

  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 tool with one optional parameter, no output schema, and no annotations, the description compensates fully: it enumerates the return fields with units (substituting for output schema docs), states freshness, and explains both call modes. Nothing an agent needs to invoke it correctly 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%, so the baseline is 3. The description's parameter text ('Omit to get all') essentially duplicates the schema's own wording and adds nothing beyond it — the case-insensitivity, ASCII-fold behavior, and examples all live in the schema. The field/unit list describes output, not parameters, so it doesn't lift this score.

  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 (get), resource (current synoptic weather observations), and origin (IMGW) in the first sentence. It clearly differentiates from siblings: get_hydro/get_warnings are for other data types, and list_weather_stations/list_hydro_stations serve listing purposes, while this tool returns current observations. The 'current' qualifier further distinguishes it from the station listing 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?

  Clearly explains the two invocation modes (omit station for all ~60, provide station for a single one), which is the core usage decision. It does not explicitly name sibling alternatives or state when NOT to use this tool, but for a simple retrieval tool the context is sufficient and the scoping behavior is unambiguous.

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