datasets_airbnb_search

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

No annotations are provided, so the description carries the full burden. It discloses key behaviors: thin cells are suppressed, group_by and sort enums, page_size constraint (page*page_size <= 10000), and freshness filters. This adds significant context beyond the parameter schema.

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 fairly concise at 4 sentences, front-loading the purpose. However, it could be slightly more structured, and the third sentence about suppression is a bit standalone without connecting to specific parameters.

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 (11 parameters, all documented in schema) and no output schema, the description is reasonably complete. It covers key constraints (page_size cap, suppression, group_by dimension) and data nature. Could mention pagination traits or default sorting, but overall satisfactory.

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 some value by explaining 'thin cells are suppressed' (related to min_listings) and reiterating enum options, but it does not significantly enhance understanding beyond 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 that the tool searches the Airbnb markets dataset and returns aggregate market rollups. It explicitly distinguishes from siblings by noting that results are aggregate-only (market cells, not individual listings), which differentiates it from tools like 'airbnb_search' that likely return individual listings.

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 on when to use the tool (for aggregate market data) and implicitly distinguishes from sibling tools by stating it returns rollups, not individual listings. However, it does not explicitly state when not to use it or list alternative tools for specific cases.

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