airbnb_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. It mentions 'pagination' (via the cursor parameter) and 'direct links to the user', which adds some context beyond the schema. However, it lacks critical details like rate limits, authentication needs, error handling, or what the search results look like (e.g., format, size limits). For a search tool with 12 parameters and no annotations, this is insufficient.

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, efficient sentence that front-loads the core purpose ('Search for Airbnb listings') and adds key details ('with various filters and pagination. Provide direct links to the user'). There's no wasted text, and it's appropriately sized for the tool's complexity.

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 (12 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the output format, error conditions, or provide enough behavioral context for safe and effective use. The mention of 'direct links' is helpful but insufficient to cover the gaps in parameter documentation and behavioral transparency.

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 0%, so the description must compensate. It mentions 'various filters' which hints at parameters like location, dates, and price, but doesn't explain any specific parameters (e.g., what 'placeId' vs 'location' means, format for 'checkin'/'checkout', what 'ignoreRobotsText' does). With 12 undocumented parameters, the description adds minimal semantic value beyond the schema's property names.

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 the verb ('Search') and resource ('Airbnb listings'), and mentions filters and pagination which differentiates it from the sibling tool 'airbnb_listing_details' that likely fetches details for a specific listing. However, it doesn't explicitly contrast with the sibling tool, so it's not a perfect 5.

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 mentions 'various filters and pagination' which implies usage for searching, but provides no explicit guidance on when to use this tool versus 'airbnb_listing_details' or other alternatives. There's no mention of prerequisites, constraints, or specific scenarios for tool selection.

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