Server Quality Checklist

Tool Scores

• amadeus_hotel_listA
  3.5/5.0
  Behavior2/5

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

  No annotations are provided, and the description does not disclose behavioral traits such as whether it is read-only, rate limits, or authentication requirements. The tool likely performs an API call, but this is not clarified.

  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 concise with a clear purpose followed by examples. It is front-loaded and efficient, though slightly verbose in listing examples.

  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?

  With no output schema, the description should explain the return format or content. It does not mention what the response contains, such as hotel IDs or details, leaving a gap for the agent.

  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 baseline is 3. The description adds examples and emphasizes valid IATA codes, adding some value, but does not provide substantial additional 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 clearly states the tool searches for hotels in a specific city and retrieves a list. It specifies the main filter options, distinguishing it from siblings like booking and search.

  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 indicates the tool is useful for getting an overview of accommodation options, providing context. However, it does not explicitly state when not to use it or list alternatives among siblings.

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

• amadeus_hotel_bookingA
  3.6/5.0
  Behavior2/5

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

  No annotations are provided, so the description must fully disclose behavior. It merely states 'book' and 'actual reservation,' but omits critical details like irreversibility, idempotency, required permissions, or side effects. This is insufficient for a mutating tool.

  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 extremely concise with two sentences, no redundant words, and front-loads the core action ('Book a hotel offer'). Every phrase earns its place.

  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?

  The tool has nested parameters and no output schema. The description does not explain the return value (e.g., booking confirmation ID) or any constraints like guest limits, making it incomplete for an operation that produces a real-world effect.

  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% with each parameter having a description. The tool description adds no new information beyond the schema, so it meets baseline but does not enrich parameter understanding.

  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's verb ('Book') and resource ('hotel offer'), explicitly distinguishing it from sibling tools (list, offer, search) by indicating it creates an actual reservation using a prior search result.

  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 that the tool uses an offer ID from a previous search, implying a sequential workflow. However, it does not explicitly mention when not to use it or list alternatives, lacking full exclusions.

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

• amadeus_hotel_searchA
  3.9/5.0
  Behavior3/5

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

  Description mentions the output includes pricing, room types, board options, and cancellation policies, but lacks information on pagination, rate limits, or actions if no results. Since no annotations exist, it carries the full burden, and more transparency would be beneficial.

  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?

  Description is a paragraph followed by four examples. It front-loads the purpose and is reasonably concise, though examples take space. Each sentence serves a clear function.

  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?

  With 13 parameters and no output schema, the description covers the main behavior (pricing and availability), lists key filters, and provides examples for typical use. It lacks details on error scenarios or output structure, but is adequate for a search tool.

  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?

  Input schema has 100% coverage, so baseline is 3. Description adds value through examples showing parameter usage, but does not explain parameters beyond what schema already provides. No additional semantic depth.

  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 'Search for hotel offers (available rooms with pricing)' with specific verb and resource. It distinguishes from sibling tools like amadeus_hotel_booking, amadeus_hotel_list, and amadeus_hotel_offer by focusing on search/pricing.

  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?

  Provides clear guidance to use valid IATA codes and shows multiple examples. However, it does not explicitly say when not to use this tool versus siblings, nor does it exclude alternative tools.

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

• amadeus_hotel_offerA
  4/5.0
  Behavior3/5

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

  With no annotations provided, the description must fully convey behavior. It indicates this is a read operation (get details) but does not mention authentication requirements, rate limits, or what happens if the ID is invalid. The behavioral coverage is adequate but not comprehensive.

  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-loading the primary action. Every sentence adds value, and there is no redundant or unnecessary information.

  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 simplicity of the tool (one parameter, no output schema), the description adequately explains the purpose and returned content (updated availability and pricing). It could mention potential errors or missing IDs, but overall it is complete enough for a get-detail operation.

  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% for the single parameter 'offerId', which already describes it as the unique identifier from a previous search. The tool description adds no additional meaning beyond what the schema provides, so a 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 'Get detailed information' and the resource 'specific hotel offer using its ID'. It also distinguishes the tool by mentioning it is for offers from a previous search result, differentiating it from sibling tools like search or list.

  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 implies usage after a previous search ('offer that was found in a previous search result'), providing clear context. However, it does not explicitly state when not to use this tool or name alternatives, leaving room for ambiguity.

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