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' and 'Provide direct links to the user,' which adds some context beyond basic functionality. However, it lacks critical details such as rate limits, authentication requirements, error handling, or what the output looks like (e.g., format of results). For a search tool with 12 parameters and no annotations, this is a significant gap in transparency.

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 and front-loaded, consisting of two sentences that directly state the tool's purpose and a key output behavior. There's no wasted verbiage or redundancy. However, it could be slightly more structured by explicitly separating functionality from output guidance, but it remains efficient and clear.

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 covers basic purpose and hints at output behavior but lacks details on result format, error cases, usage constraints, or how to interpret pagination. Without annotations or an output schema, the agent has insufficient information to fully understand the tool's behavior and integration needs.

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?

The input schema has 100% description coverage, so all parameters are documented in the schema itself. The description adds minimal value beyond the schema by mentioning 'various filters and pagination,' which loosely maps to parameters like location, dates, prices, and cursor. However, it doesn't provide additional semantics, constraints, or examples that aren't already in the schema descriptions, meeting the baseline for high schema coverage.

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'), which is specific and actionable. However, it doesn't explicitly differentiate from its sibling tool 'airbnb_listing_details', which likely provides details for specific listings 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 provides minimal usage guidance. It mentions 'Provide direct links to the user,' which hints at output behavior but doesn't specify when to use this tool versus alternatives like the sibling 'airbnb_listing_details' or other search methods. There's no explicit guidance on prerequisites, when-not-to-use scenarios, or comparisons to other tools, leaving the agent to infer usage context.

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