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 'Provide direct links to the user,' which adds some context about output behavior. However, it lacks critical details such as rate limits, authentication requirements, error handling, or what the search results include (e.g., format, fields). For a search tool with 12 parameters, 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 concise with two sentences that are front-loaded: the first states the core purpose, and the second adds output context. There's no wasted text, but it could be slightly more structured (e.g., separating purpose from behavioral notes).

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 output schema, no annotations), the description is incomplete. It lacks details on output format (beyond 'direct links'), error cases, authentication, or rate limits. For a search tool with many filters and pagination, more context is needed to guide effective use by an AI agent.

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 schema fully documents all 12 parameters. The description adds minimal value beyond the schema, mentioning 'various filters and pagination' which aligns with parameters like location, dates, prices, and cursor. It doesn't provide additional syntax, format details, or usage examples beyond what's in the schema descriptions.

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 tool's purpose: 'Search for Airbnb listings with various filters and pagination.' It specifies the verb ('search'), resource ('Airbnb listings'), and scope ('with various filters and pagination'). However, it doesn't explicitly differentiate from its sibling tool 'airbnb_listing_details' beyond the general search vs. details distinction.

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 no guidance on when to use this tool versus alternatives. It mentions 'Provide direct links to the user,' which hints at output format but doesn't clarify usage context, prerequisites, or exclusions. There's no mention of when to choose this over 'airbnb_listing_details' or other potential tools.

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