airbnb_listing_details

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

With no annotations, the description carries the full burden. It states it gets details and provides links, but does not disclose any behavioral traits such as whether it is read-only, if it makes external requests, error handling, or rate limits. It lacks important context for an AI agent to assess risks.

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?

Two sentences, no unnecessary words. Could be slightly more structured (e.g., listing expected outputs), but it is concise and front-loaded with the purpose.

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 8 parameters, no output schema, and no sibling differentiation in description, the description is incomplete. It does not explain what 'detailed information' includes, how errors are handled, or usage considerations like API limits or data freshness. This leaves gaps for the agent.

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 100%, so baseline is 3. The description adds no additional meaning beyond what the parameter descriptions in the schema provide. It does not explain how parameters like check-in/out or guests affect the returned data.

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 action 'Get detailed information' and the resource 'specific Airbnb listing', and adds 'Provide direct links', which is a distinct output. It differentiates from the sibling 'airbnb_search' tool by implying it returns details for one listing.

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 implies using this tool when you have a specific listing ID and want details/links, but it does not explicitly state when to avoid it or mention the sibling tool as an alternative for searching. No exclusion criteria are given.

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