airbnb_listings_search

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

No annotations are provided, so the description carries the full behavioral burden, and it delivers almost nothing: no note on data freshness, rate limits, scraping behavior, or whether results are cached. The mention of the backing repo (captainhandsome/airbnb-listings-search) is provenance metadata, not behavioral context an agent can act on.

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 short sentences with the purpose front-loaded and no filler. The trailing sentence about the backing implementation is of marginal value to an agent and is the one piece that could be dropped.

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 two-parameter search with no output schema and no annotations, the definition is minimally adequate but leaves gaps: it never describes the shape of returned results (per-listing fields, price units, occupancy semantics) or pagination/limit behavior, all of which an agent would need to interpret output.

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 50%: location has an example, but max_results is undocumented and its effect on the response is never explained. The description adds no parameter meaning at all, so it fails to compensate for the coverage gap, though the default of 10 makes max_results semi-self-explanatory.

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?

States a specific verb (Search) and resource (short-term rental listings, nightly prices, occupancy from Airbnb), which plainly distinguishes it from marketplace siblings like google_maps_search or glassdoor_jobs_search. It stops short of noting scope limits or differentiating explicitly from generic search tools, but the domain is 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?

There is no statement of when to use this tool versus alternatives, no exclusions, and no prerequisites. A reader can infer it is for Airbnb rental lookups from the name alone, but the description supplies no routing guidance.

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