airbnb_listing_details

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions returning 'detailed information' and 'direct links', which hints at read-only behavior and output format, but fails to address critical aspects like rate limits, authentication needs, error handling, or data freshness. For a tool with 8 parameters and no annotation coverage, this is insufficient.

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 brief and front-loaded, stating the core purpose in the first sentence. The second sentence adds a usage hint without redundancy. However, it could be more structured by explicitly separating purpose from guidelines, and the vague phrase 'Provide direct links to the user' slightly reduces clarity.

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 tool's complexity (8 parameters, no output schema, no annotations), the description is incomplete. It lacks details on return values, error conditions, performance expectations, and how parameters like dates affect results. Without annotations or output schema, the description should compensate more to ensure the agent can use the tool effectively.

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 description adds no parameter-specific information beyond what's already in the schema, which has 100% coverage with clear descriptions for all 8 parameters. This meets the baseline for high schema coverage, but the description doesn't enhance understanding of parameter interactions or provide examples, limiting its added value.

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'), making the intent unambiguous. However, it doesn't explicitly differentiate from its sibling 'airbnb_search' (which likely searches for listings rather than retrieving details for a specific one), preventing a perfect score.

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' suggests a use case for sharing results, but it offers no explicit advice on when to use this tool versus alternatives like 'airbnb_search'. There's no mention of prerequisites, exclusions, or contextual best practices, leaving significant gaps in usage direction.

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