Server Quality Checklist

Tool Scores

• getCityWeatherB
  3.1/5.0
  Behavior2/5

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

  With no annotations, the description alone carries the burden of behavioral disclosure. It states only that it fetches current weather and gives no context about data source, units (metric/imperial), response format, error handling for unknown cities, or whether the result is cached/real-time. This is a significant omission for a tool with no structured 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 a single, front-loaded sentence with zero redundant words. It conveys the core action efficiently and appropriately for such a simple tool.

  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?

  For a tool with only one simple parameter and no output schema, the description is nearly sufficient. However, it lacks any note about what the response contains (e.g., temperature, humidity) or what happens if the city is not found, leaving a small but real gap for agent decision-making.

  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 fully documents the only parameter ('name') with a clear example ('City name, e.g. Delhi'), giving 100% schema coverage. The description merely echoes 'city' without adding format constraints or additional 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 uses a clear verb ('Fetch') and a specific resource ('current weather for a city'), which unambiguously states what the tool does. Since there are no sibling tools, it doesn't need to differentiate itself, though it could have specified what weather attributes are returned.

  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 provides no guidance on when to use this tool versus any alternative (none are listed). It doesn't mention any constraints like acceptable city name formats, typical use cases, or exclusivity with other weather methods.

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