Search Expedia destinations by free-text term and get normalized typeahead suggestions for cities, airports, neighborhoods, and hotels.
Search Expedia destinations. Returns normalized destination/property typeahead suggestions (cities, airports, neighborhoods, hotels) for a free-text term.
| Name | Required | Description | Default |
|---|---|---|---|
| option | Yes | Location search payload |
Changes observed during successful MCP inspections.
v1.17.5Input schema / properties / option / propertiesAdded value: +{
+ "currency": {
+ "type": "string"
+ },
+ "locale": {
+ "type": "string"
+ },
+ "term": {
+ "type": "string"
+ }
+}Input schema / properties / option / requiredAdded value: +[
+ "term"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With zero annotations, the description carries the full disclosure burden. It does convey read-only behavior ('returns ... suggestions') and adds the useful qualifier that results are 'normalized'. However it does not disclose result limits, ordering, response entry shape, or behavior on unmatched terms - gaps that matter for a typeahead tool with no annotation safety net.
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 sentences with no wasted words. The action verb and resource lead, and the return-type detail follows immediately. Every phrase (typeahead, normalized, entity list, free-text) 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 tool with one nested parameter and no output schema, the description covers the core invocation (search destinations by free-text term) but omits useful context: what fields each suggestion contains, whether the returned ID feeds downstream tools like expedia_properties_search, and the purpose of the optional locale/currency fields. Adequate but with clear 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?
Schema description coverage is 100%, so the baseline is 3. The description adds modest value by clarifying that `term` is free-text input, which is a meaningful semantic for a typeahead. However `locale` and `currency` receive no explanation in either schema or description, so their effect on results is left to inference.
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 a specific verb+resource ('Search Expedia destinations') and specifies the return type ('normalized destination/property typeahead suggestions') and the entity kinds covered (cities, airports, neighborhoods, hotels). This clearly differentiates it from Expedia siblings like expedia_properties_search (actual property listings), expedia_flights_search, and expedia_activities_search.
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?
Usage is implied but not explicit. The phrase 'typeahead suggestions' hints that this is the autocomplete/first-step look-up rather than a full property search, but the description never names alternatives or states when to use expedia_properties_search vs this tool. An agent must infer the routing decision from the word 'typeahead' alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.