airbnb_property: GET /

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

With no annotations, the description carries the full burden. The tool name 'Get' implies read-only, but the description does not confirm it is non-destructive, nor does it mention rate limits, authentication needs, or what happens on failure. This lack of explicit behavioral disclosure is a significant gap for a data-fetching tool.

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 moderately concise, starting with the action and listing the return fields efficiently. It could be slightly tighter, but it is well-structured and avoids unnecessary words, earning a score of 4.

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 of the tool (returns a rich set of property details) and no output schema, the description comprehensively lists the data fields. However, it omits potential error conditions (e.g., invalid URL) and behavioral notes, which would enhance completeness. Overall, it covers the main use cases and outputs well.

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 schema has 100% coverage (one parameter, 'url', with a clear description). The description adds context about using the URL to fetch the property page but does not provide additional semantic detail beyond the schema. Baseline score of 3 is appropriate.

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 fetches full Airbnb property details by listing URL, lists specific return fields (title, description, location, coordinates, price, fees, ratings, etc.), and distinguishes it from the sibling 'listing-search' endpoint by emphasizing deep-dive enrichment. This provides a specific verb+resource+scope.

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 explicitly recommends use for travel-planning agents, deep-dive rate research, photo/amenity enrichment of listings from the listing-search endpoint, and compliance audits. It implies appropriate contexts but does not explicitly state when not to use it or mention alternatives beyond the listing-search endpoint.

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