airbnb_property: GET /

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

With no annotations available, the description itself communicates read-only fetch behavior: 'Fetches the full Airbnb property page' and the title 'GET /' reinforce that no state change occurs. It also documents the expected response scope, though it does not cover optional caveats such as rate limits, stale data, or invalid URL handling.

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 efficient and front-loaded with the primary behavior, followed by a compact but useful list of returned fields and use cases. The long return-value list earned to be somewhat dense, but it is made of specific useful information rather than filler.

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?

For a one-parameter fetch tool without output schema, this description supplies strong coverage of what the tool returns and why it should be used. It could be even more complete with an explicit 'if you need richer listing search, use getAirbnbListings' condition, but overall it gives the agent nearly everything needed to route and invoke it correctly.

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 single `url` parameter is already fully described in the schema. The description adds meaning by connecting the URL to the action ('fetches by listing URL'), but it does not provide example formats, normalization rules, or other parameter-level insight beyond what the schema already exposes.

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 explicitly states what the tool does: it fetches a complete Airbnb property details by listing URL and gives a concrete list of returned fields. It also contrasts itself with the listing-search sibling by framing the request as an enrichment of listings found via the listing-search endpoint.

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 identifies concrete use cases: travel planning, deep-dive rate research, listing enrichment, and compliance/audit checks. It also hints at the relationship to the listing-search endpoint, but it does not give an explicit 'do not use this when...' instruction or name the sibling alternative.

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