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

The tool is described as a read-oriented search operation that 'returns' listing data, and no side effects are implied. However, with no annotations, it does not explicitly state that it is non-mutating, nor does it mention rate limits or error behavior.

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 well-organized and front-loaded with the tool's purpose, followed by output details and use cases. It is slightly verbose with repeated phrases and use-case enumeration, but still efficient and easy to scan.

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?

The description covers the main invocation patterns, required and optional input categories, pagination, and a broad list of returned fields. Since there is no output schema and annotations are absent, it carries a heavier burden; it could be more complete by specifying date format and the exact relationship between check-in and check-out requirements.

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 complete and parameter descriptions add useful semantics, especially the requirement that location is needed unless all four bounding-box coordinates are provided. Missing details such as date format and the exact required combination of check-in/check-out slightly reduce the score.

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 identifies the tool as a search operation for Airbnb listings by location or bounding box and date range, and enumerates the returned data. Its listing-focused scope is easily distinguished from the sibling property-details tool.

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 concrete use cases and explains the two main search modes (location vs. bounding box), along with pagination via nextPageToken. It does not explicitly contrast the sibling property-details tool, but the intended usage context is still clear.

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