datasets_vehicle_listings_search

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it delivers: it reveals the crawled-index nature, the coverage asymmetry between CarMax (fully enumerable) and Autotrader/Cars.com (best-effort), the location-approximation behavior for non-CarMax sources, and seller_type sparsity ("not populated for every row"). These are genuine behavioral traits an agent could not infer from the schema. Minor gaps remain — default ordering when sort is unspecified and response shape — but the data-quality disclosures are substantive.

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 purpose is correctly front-loaded, but the body is a dense single run-on paragraph that packs source caveats, location approximation, seller_type sparsity, and the sort enum into one unbroken stretch of text. Every piece of information earns its place, yet the lack of sentence boundaries and structure hurts scannability for an agent parsing the description quickly.

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 22-parameter, zero-required tool with no output schema and no annotations, the description covers data-quality caveats well but leaves notable gaps: it does not explain how filters combine (AND semantics), what an unfiltered query returns, how result ordering behaves with no sort specified, or what the response structure looks like. The pointer to "see the dataset markdown" acknowledges that essential documentation lives outside the description. It also does not route agents to related sibling tools like datasets_vehicle_listings_facets or datasets_vehicle_listings_price_history.

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 real value beyond the schema by unpacking the source enum semantics (explaining what each marketplace value means for coverage completeness), flagging that seller_type is not reliably populated, and enumerating the full sort enum. This is exactly the kind of parameter-level meaning the schema's one-line descriptions do not convey.

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 opens with a clear verb+resource pairing: "Search vehicle listings dataset" followed by "Searches the crawled used-vehicle listings index," which names a specific indexed resource. It is distinguishable from sibling dataset tools like datasets_vehicle_listings_facets, datasets_vehicle_listings_item, and datasets_vehicle_listings_price_history by its search action, but it never explicitly names those alternatives, so differentiation relies partly on the tool name rather than the description itself.

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 substantial usage-relevant context on data quality: CarMax inventory is "fully enumerable (re-crawled on a standing schedule)" while "Autotrader/Cars.com coverage is a best-effort zip-code sweep, not exhaustive," and it warns that those rows approximate location rather than the seller's exact address. This tells the agent when results are trustworthy, but it does not explicitly state when to use this tool versus alternatives, when not to use it, or how it relates to sibling search tools like carmax_search or carsdotcom_search.

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