ATA Travel

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

Annotations already indicate non-read-only and side effects (readOnlyHint=false, openWorldHint=true). The description adds valuable context: it creates inventory-holding provisional bookings or enquiry holds, includes traveler communication instructions, and notes next steps. No contradictions with annotations.

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

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

The description is a single paragraph that packs multiple details (prerequisites, scenarios, traveler instructions). It is not overly long but could be more structured (e.g., bullet points for different scenarios) to improve readability. Every sentence adds value, but conciseness is moderate.

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

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

Given the complexity (17 parameters, no output schema, openWorldHint), the description covers the overall flow and two outcomes but lacks details on response format, error handling, and full parameter semantics. It does not fully equip an AI agent to use the tool correctly in all scenarios.

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

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

Schema description coverage is only 35%, and while the description mentions key parameters like guestName, guestEmail, travelerAssertion, and agentHandoffId, it does not explain many required fields such as propertyToken, roomId, checkIn, checkOut, and adults. The description adds some context but insufficiently compensates for the low coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Secure a reservation or create a host-approval enquiry on behalf of a traveler.' It specifies two main use cases and distinguishes the tool from siblings like create_quote by focusing on provisional bookings and enquiries.

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

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

The description provides prerequisites (guest name/email plus travelerAssertion or agentHandoffId) and scenario-based guidance (instant book enabled vs disabled). However, it does not explicitly contrast with sibling tools or state when not to use this tool, leaving some ambiguity for an AI agent to choose.

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

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

Adds value beyond annotations by stating quotes are non-binding and do not hold inventory. No contradiction with annotations (readOnlyHint=false). Could mention side effects or success/failure responses.

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

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

Description is concise with no waste, front-loaded with purpose. However, it is a single long sentence that could be split for better readability.

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

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

Given 16 parameters and no output schema, the description explains the output nature and constraints but lacks details on many parameters like priceAudience and selectedRoomCount. Adequate but not comprehensive.

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

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

Describes key parameters like guestName, guestEmail, travelerAssertion, agentHandoffId, but schema coverage is only 31% and many parameters (e.g., propertyToken, roomId, checkIn, checkOut) lack explanation. Baseline 3 due to low coverage but adds some meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool generates a 'non-binding reference quote' for a traveler, using specific verbs and resources. It differentiates from sibling create_provisional_booking by noting quotes do not hold inventory or guarantee availability.

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

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

Specifies required inputs (guest name/email plus travelerAssertion or agentHandoffId) and provides guidance for verification interactions. However, it does not explicitly exclude alternatives like create_provisional_booking for when a booking is needed.

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

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

The description adds value beyond annotations by detailing the content of the response (assigned stays and map coordinates). It is consistent with annotations and provides a clear picture of the tool's behavior.

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

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

The description is extremely concise: two sentences with no filler. The first sentence covers purpose and return, the second gives usage context. Every statement earns its place.

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

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

For a simple read-only tool with one parameter and no output schema, the description is sufficient to select and invoke the tool correctly. It could be slightly improved by noting that the tool is read-only (though annotations cover this), but overall it is complete enough.

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

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

With 0% schema description coverage, the description does not add meaning beyond the schema for the 'slug' parameter. It only mentions the source of the slug but lacks details on format, constraints, or examples, leaving the agent to infer from context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and the resource 'ATA building/complex profile', and explicitly lists what is returned (assigned stays and map coordinates). It distinguishes from siblings by specifying the source of the slug, making it clear when to use this tool.

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

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

The description advises to use a slug from 'search_buildings or property search results', providing clear context on how to obtain the required input. However, it does not explicitly mention when not to use this tool or suggest alternatives from the sibling list.

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

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

Annotations provide safety profile (readOnly, idempotent, not destructive). Description adds context on exact output (mission and description), but no further behavioral details needed.

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

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

Two concise sentences, front-loaded with action. No wasted words.

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

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

Simple tool with no output schema; description explains return value. Complete for its purpose.

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

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

No parameters; baseline 4 per rubric. Description appropriately omits param info as none exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Description uses specific verb 'Returns' and clearly identifies resource 'ATA company mission and description'. Distinguishes from siblings as no other tool provides company info.

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

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

Explicitly states when to call: when user asks about ATA, what we do, vision, or company. Provides clear context for use.

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

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

Annotations already cover key behavioral traits (readOnlyHint, idempotentHint, etc.). The description adds that the summary is 'live' and lists included elements, but does not provide extra details like response format or data freshness beyond what annotations imply. It does not contradict annotations.

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

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

The description is highly concise with two sentences: the first defines the output, the second states the recommended use case. Every sentence adds value without redundancy.

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

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

Given no parameters and no output schema, the description provides a good overview of what the summary contains (destinations, stay types, etc.). However, it lacks details on the output structure or format, which would enhance completeness. Still mostly adequate.

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

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

There are zero parameters, so schema coverage is 100%. The description adds no parameter-specific info, which is acceptable. Baseline score of 4 applies per guidelines.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns a 'compact, live summary' of specific network attributes (destinations, stay types, etc.), using a strong verb and resource pairing. It distinguishes itself from sibling tools like search_buildings by indicating it provides an overview before offering discovery shortcuts.

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

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

The description explicitly advises using this tool 'before offering discovery shortcuts or asking a vague traveler to choose from options,' providing clear context. While it does not list alternatives or exclusion cases, the usage scenario is well-defined.

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

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

Annotations already indicate readOnlyHint=true, idempotent, non-destructive. Description adds specific behavioral details about the response (image gallery, room images, links), which is 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.

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

One concise sentence covering purpose, content, and parameter usage. Could be slightly more structured but is efficient and front-loaded.

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

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

For a simple retrieval tool with one parameter, annotations, and no output schema, the description adequately covers purpose, parameter source, and expected response contents. Lacks some detail on response format but is sufficient.

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

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

Single parameter 'propertyToken' has 0% schema coverage, but description explains its origin ('from search results'), compensating and adding meaning beyond the schema's type-only definition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it gets detailed property information including image gallery, room images, and links. Distinguishes from siblings like get_building_details and search_buildings.

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

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

Explicitly says 'Use propertyToken from search results', providing clear context for when to use this tool. Does not mention alternatives or when not to use, but usage is well implied.

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

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive. The description adds the fact that it returns stays tied to a published building with optional filters, which is consistent but not significantly 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.

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

Single sentence, 15 words, no redundancy. All information is front-loaded and justified.

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

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

Despite good annotations and concise purpose, the description lacks details on return format, meaning of 'ATA', edge cases, and how to properly use the 8 parameters. For a tool with no output schema and low parameter coverage, this is insufficient.

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

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

Schema coverage is only 13% (one parameter described). The description hints at date and guest count filters, partially compensating, but does not explain critical parameters like slug, priceAudience, internalAgentKey, or the enum values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'Return' and resource 'ATA stays assigned to a published building'. It clearly states the main action and scope. While 'ATA' is undefined, the overall purpose is clear and distinct from siblings like get_building_details and search_buildings.

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

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. The description mentions optional filtering but does not compare to other tools like search_property_availability or mention prerequisites (e.g., building must be published).

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

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

Annotations already indicate readOnlyHint and idempotentHint. The description adds that it is an 'internal' status check performed after sending a link, and includes a user-facing caution (not to mention polling to the traveler). This adds behavioral 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.

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

The description consists of two sentences: the first states purpose, the second provides a critical usage constraint. Both are concise and essential, with no unnecessary words.

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

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

Given the tool's simplicity (one parameter, no output schema), the description covers the main purpose, usage context, and a key user protocol. However, it does not describe the output format (e.g., what status is returned), which would be helpful without an output schema.

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

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

Schema description coverage is 100% and the single parameter 'handoffId' is well-described in the schema as 'ID returned by start_traveler_handoff.' The description does not add new semantics beyond confirming the parameter's origin. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: checking the internal status after sending an ATA verification link to see if the traveler clicked the link. It distinguishes itself from siblings like start_traveler_handoff and get_traveler_memories.

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

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

The description provides a clear use case ('Use to know whether the traveler clicked the link') and an important exclusion ('Do not mention this tool... to the traveler'). It does not explicitly mention when not to use or alternatives, but the context is well-defined.

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

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds no further behavioral details beyond the action itself, missing context about data format, performance, 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.

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

The description is two sentences, front-loaded with the purpose, and contains no unnecessary words. Every sentence serves a clear function.

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

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

For a simple tool with one parameter and no output schema, the description covers the essential purpose and usage context. It could mention output structure but is sufficient given annotations and sibling differentiation.

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

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

The input schema has 100% coverage with a description for 'travelerId'. The tool description does not add any additional parameter information beyond what the schema already provides, so it meets the baseline but adds no extra value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns 'active structured memories for a verified traveler', using a specific verb and resource. It is distinct from siblings like 'suggest_traveler_memory' which suggests memories rather than retrieving them.

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

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

The description explicitly says 'Use this when you need durable personalization beyond the context already provided', providing clear when-to-use guidance. It does not explicitly state when not to use or list alternatives, but the context is sufficient.

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

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds that the tool returns read-only offer details and secure public purchase links, reinforcing the behavioral traits but not adding significant new behavioral 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.

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

The description is two sentences, front-loaded with the main purpose, and includes a key behavioral note. No extraneous information.

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

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

With no output schema, the description only states that returns offer details and purchase links, lacking specifics about the structure or fields returned. For a listing tool, this is minimally adequate but could be more complete.

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

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

Schema description coverage is 67% (2 of 3 parameters described). The tool description does not add any parameter-level details, so the parameter semantics rely entirely on the schema. Baseline 3 is appropriate as it neither enhances nor detracts.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists published extras for a known ATA property, listing specific types (day passes, experiences, etc.) and noting it returns read-only details and purchase links. It distinguishes itself from create tools by explicitly saying it does not create an order.

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

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

The description implies usage for retrieving offer details and purchase links without creating an order, which differentiates from sibling creation tools. However, it does not provide explicit when-to-use/when-not-to-use guidance relative to other listing or search tools (e.g., search_property_catalog).

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

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

Annotations fully cover behavioral traits (readOnlyHint, idempotentHint, etc.). The description adds no new behavioral context beyond stating it is simple, which is acceptable given that annotations are rich and not contradicted.

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

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

The description is a single sentence with no extraneous information. It is highly concise and front-loaded.

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

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

Given zero parameters and comprehensive annotations, the description is largely complete for a ping tool. However, mentioning expected return value (e.g., 'pong') would improve completeness.

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

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

The tool has zero parameters, so the description does not need to add parameter details. Baseline score of 4 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it is a 'simple ping tool', clearly indicating a connectivity test. The verb 'ping' and resource 'tool' are specific, and it is easily distinguishable from sibling tools that perform data operations.

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

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

No explicit when-to-use or alternative guidance is provided. Usage is implied by the name 'ping' (check connectivity), but the description does not clarify when it should be used over other tools.

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

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds context about searchable dimensions (destination, neighborhood, tag, amenity, free-text). However, it does not describe behavior like result ordering or pagination. With annotations covering safety and idempotency, a 3 is appropriate.

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

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

The description is two sentences, front-loaded with purpose, and contains no extraneous information. Every sentence adds value.

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

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

Given the tool's search nature, the description covers the key search dimensions and usage context. Annotations provide behavioral safety. However, absence of output schema and lack of detail on result format or pagination slightly reduce completeness. Still, it is sufficient for an agent to select and invoke the tool correctly.

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

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

Schema coverage is low (17%: only 'query' has a description). The description partially compensates by listing search dimensions (destination, neighborhood, tag, amenity, free-text) that map to parameters. However, it does not detail parameter format or constraints, and missing descriptions for 'city', 'tags', 'amenities', 'neighborhood', and 'maxResults' reduce clarity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Find' and the resource 'published ATA building/complex profiles', and lists search criteria. It distinguishes from siblings by specifying use for buildings, complexes, neighborhoods, etc., which are not covered by other tools like get_building_details or search_property_catalog.

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

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

The description explicitly says 'Use this for questions about buildings...' and lists example use cases. It provides clear context for when to use the tool, though it does not explicitly mention when not to use it or list specific alternatives.

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

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds value by detailing default values (window, nights, adults) and clarifying that preferences are soft ranking signals, which goes beyond annotation-provided traits.

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

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

The description is two sentences, front-loaded with purpose and defaults, then clarifying preference behavior. No wasted words; every sentence earns its place.

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

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

For a search tool with 16 parameters and no output schema, the description does not explain return format, sorting, or result structure. It adequately covers input behavior but misses output expectations, leaving the agent partially uninformed.

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

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

Schema coverage is 88%, so many parameters already have descriptions. The description adds nuance about preferences being 'soft ranking signals, not a closed taxonomy', but largely reiterates defaults already present in schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb-resource combination ('Find real, priced ATA stays') and explicitly includes the key differentiator 'when the traveler is flexible', distinguishing it from siblings like search_network_availability and search_property_availability.

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

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

The description gives a clear context ('when the traveler is flexible') and mentions defaults, but does not explicitly state when not to use this tool versus alternatives (e.g., fixed-date searches). Usage guidance is implied rather than explicit.

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

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds that it provides 'real-time pricing,' which adds value by indicating data freshness. It does not contradict annotations and offers useful context beyond the structured hints.

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

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

Three focused sentences with no wasted words. Front-loaded with the primary action, then usage condition, then supported features. Every sentence adds value, and the structure is logical and scannable.

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

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

Given 15 parameters, no output schema, and the tool's complexity, the description covers the main purpose, usage condition, and key filters. It does not explain return format or pagination, but for a read-only search tool with extensive schema descriptions, it is reasonably complete.

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

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

With 87% schema coverage, the schema already documents most parameters. The description adds practical usage hints for keyword ('vibe searches'), location ('omit when traveler knows dates but is open'), and lists filtering categories, providing additional meaning not present in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it finds accommodations with real-time pricing, specifying the ATA Travel Network. It distinguishes from siblings like search_flexible_network_availability by noting 'when dates are known' and lists filtering options, making the tool's purpose specific and unambiguous.

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

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

Explicitly states 'Use when dates are known,' providing a clear condition for use. This implies when dates are not known, alternatives like search_flexible_network_availability should be used. However, it does not explicitly mention when not to use the tool or name alternative siblings, leaving some ambiguity.

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

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description's minimal addition of 'Search specific dates and occupancy' does not provide extra behavioral context 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.

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

The description is a single concise sentence with no wasted words, but could be slightly more informative without losing conciseness.

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

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

With 8 parameters, no output schema, and no description of return values, the description is too sparse for a moderately complex tool. Missing guidance on output format or behavior.

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

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

Schema description coverage is 50%, but the description adds no parameter-level detail. It does not compensate for undocumented parameters like adults, children, or priceAudience.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches availability for a known property using its propertyToken, distinguishing it from sibling tools like search_buildings and search_property_catalog.

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

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

The description implies usage when a propertyToken is known but does not explicitly mention when not to use it or suggest alternatives like search_property_catalog for unknown properties.

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

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

The description discloses that the tool is fast and lightweight, and explicitly states it performs no availability or pricing check. This adds context beyond the annotations (which already indicate read-only, idempotent, non-destructive). It does not describe all behaviors (e.g., result format), but the annotations cover safety aspects.

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

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

The description is only two sentences, highly concise, and front-loads the key differentiator (no dates needed). Every sentence serves a purpose: describing the action, highlighting speed, and listing use cases.

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

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

Given 9 optional parameters and no output schema, the description provides sufficient context for the tool's purpose and usage scenarios. It explains when to use it, but does not explicitly describe the return format (e.g., list of properties without pricing). However, the context of siblings and annotations fills most gaps.

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

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

All 9 parameters have descriptions in the input schema (100% coverage), so the description adds no extra parameter semantics. The tool description does not elaborate on parameter usage beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool browses the ATA property catalog without needing dates, distinguishing it from date-dependent sibling tools like search_property_availability. It specifies the resource (property catalog) and verb (browse), and highlights key differentiators like no availability or pricing check.

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

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

The description explicitly says to use this tool for vague exploration, browsing by type/amenity/view, or when the traveler has no dates. It implies when not to use (when dates or pricing are needed) but does not name specific alternative tools, which would elevate it to a 5.

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

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

Adds context beyond annotations by describing the confirmation step and email notification behavior. However, it does not fully disclose all side effects (e.g., what happens if email fails, or if already approved). Annotations already indicate non-read-only, non-destructive nature.

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

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

Four sentences, front-loaded with purpose, and concise. Instructions are clear without redundant phrasing.

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

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

Despite 19 parameters and no output schema, the description does not cover return values or behavior for many parameters. It focuses on a few key aspects but is insufficient for complete understanding of tool actions and outcomes.

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

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

Description adds meaning for key parameters (guestEmail, emailConfirmedByTraveler, action) beyond the schema, but with 42% schema coverage, it leaves many parameters (adults, roomId, etc.) unexplained. The schema itself has some descriptions, but overall incomplete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it is an 'Internal approval step for quote or booking tools', which specifies the verb (start/handoff) and resource (traveler approval). It distinguishes from siblings like get_traveler_handoff_status by indicating initiation vs. status checking.

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

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

Provides specific instructions: read guestEmail back, confirm, set emailConfirmedByTraveler=true, and tell traveler to check inbox. However, it does not explicitly state when not to use or compare with alternatives like get_traveler_handoff_status.

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

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

The annotations indicate this is a non-read-only (write) and non-destructive operation. The description adds value by specifying 'durable' (lasting) and limiting use to explicitly stated preferences, which gives the agent clear behavioral constraints. It does not contradict any annotations and adds meaningful context about the memory's persistence and scope.

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

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

The description is extremely concise—two sentences that precisely convey the tool's purpose and usage constraints. No unnecessary words or redundant information. It earns its place efficiently.

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

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

Given the tool has 8 parameters, 5 required, and no output schema, the description covers the essential aspects: what to store (preferences/constraints) and the conditions for use (stable, explicit). It does not detail the return value or update semantics, but the absence of output schema makes this acceptable. The presence of a read sibling (get_traveler_memories) further contextualizes its role.

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

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

The input schema already describes all 8 parameters with clear descriptions (e.g., key enum, value format). The tool description does not add additional parameter-specific semantics beyond the schema, so it relies on the existing high coverage. Baseline of 3 is appropriate as the description offers no extra parameter guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Save or update') and the resource ('durable traveler memory') with a specific purpose ('for personalization'). It distinguishes from the sibling tool 'get_traveler_memories' by focusing on writing, and is sufficiently specific to avoid confusion with other write tools like 'create_provisional_booking'.

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

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

The description provides clear context: 'Use only for stable, travel-relevant preferences or constraints explicitly stated by the traveler.' This tells the agent when to use the tool (for explicit, stable memories) but does not explicitly exclude alternative tools or state when not to use it. The guideline is helpful but lacks explicit exclusionary language.

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