airbnb_listing_details

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

No annotations are provided, so the description carries the full burden. It mentions 'Get detailed information' and 'Provide direct links,' which implies a read-only operation, but it doesn't disclose behavioral traits like authentication needs, rate limits, error handling, or what 'detailed information' includes. For a tool with 8 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 appropriately sized and front-loaded: two concise sentences that directly state the tool's purpose and a key usage note. Every sentence earns its place without redundancy or fluff, making it efficient and easy to parse.

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 (8 parameters, no annotations, no output schema), the description is incomplete. It lacks details on parameter usage, return values, error conditions, and behavioral constraints. While it states the purpose clearly, it doesn't provide enough context for an agent to effectively use the tool without guesswork, especially with undocumented parameters.

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 0%, meaning none of the 8 parameters are documented in the schema. The description does not add any meaning beyond the schema—it doesn't explain what parameters like 'ignoreRobotsText' do, how dates should be formatted, or the purpose of occupancy fields. With low coverage and no compensation in the description, this fails to provide necessary parameter context.

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: 'Get detailed information about a specific Airbnb listing.' It specifies the verb ('Get') and resource ('Airbnb listing'), and distinguishes it from the sibling tool 'airbnb_search' by focusing on details for a specific listing rather than searching. However, it doesn't explicitly differentiate from the sibling beyond implied 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 provides minimal guidance: 'Provide direct links to the user' hints at usage context, but it doesn't specify when to use this tool versus 'airbnb_search' or other alternatives, nor does it mention prerequisites or exclusions. No explicit when/when-not instructions are given.

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