airbnb_search

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

With no annotations, the description must carry the behavioral burden. It does disclose a meaningful behavior beyond the schema: the tool provides direct links to the user. However, it does not mention the notable behavior around 'ignoreRobotsText' (ignoring robots.txt rules), nor any rate limits or implications of performing these searches.

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, front-loading the core action and then stating the expected output. It is efficient, though 'various filters' is somewhat vague and adds little information beyond the schema.

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 13 parameters and no output schema, the description is minimal. It covers the main purpose and the direct-link output, but it does not explain pagination behavior, the significance of the robots-related parameter, or how this tool relates to its sibling. The schema covers parameters well, so it is adequate but not 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 100%, so the baseline is 3. The description only says 'various filters and pagination,' which adds no meaningful parameter semantics beyond what the schema already provides for each parameter.

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 and resource ('Search for Airbnb listings') and adds scope with 'various filters and pagination' and an explicit output ('Provide direct links to the user'). This clearly distinguishes it from the sibling tool airbnb_listing_details, which is about retrieving details rather than searching.

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 this tool is for searching listings rather than fetching details, so the intended use is partially clear from the contrast with the sibling tool. However, it never explicitly states when to use this tool versus airbnb_listing_details, nor does it mention any search-specific prerequisites or limitations.

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