Server Quality Checklist

Tool Scores

• hasdata_google_travel_flights_getGoogleFlightsA
  3.9/5.0
  Behavior3/5

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

  With no annotations, the description carries the full burden for behavioral disclosure. It states what the search returns and implies a read-only operation, but it does not explicitly mention that no mutations occur, nor does it disclose rate limits, latency differences beyond the per-parameter deepSearch note, or any operational constraints such as result limits.

  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 front-loaded with the core action and uses three focused sentences covering operation, returned data, and use cases. The final use-case list includes some reputation-heavy phrases, but for 31 parameters the summary remains scannable and does not repeat schema content.

  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?

  There is no output schema, so the description's enumeration of returned per-itinerary fields is valuable and largely covers the response contract. Input parameters are fully documented in the schema with examples. The main gaps are the lack of pagination/error behavior and some explanation of how booking and departure tokens should be used, but these are partially covered by parameter descriptions.

  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 every parameter is already documented in the input schema. The description only groups parameter types into a summary and adds no new per-parameter semantics, yielding the baseline score for a fully covered 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?

  The description states a specific action ('Searches Google Flights') and a clear resource, and goes beyond the name by enumerating trip types, filter dimensions, and returned data. An agent can immediately understand what this tool does and what its result contract looks like.

  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 gives explicit use contexts ('travel-planning agents, fare monitoring, corporate travel dashboards, emission-aware trip optimization') and covers the major itinerary types. There are no sibling tools to compare against, so explicit when-not-to-use or alternative routing is not possible, but the intended use cases are clear.

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