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

Annotations declare readOnlyHint=true and openWorldHint=true, which already cover the safe read nature. The description adds that it returns specific data fields, but it does not disclose any additional behavioral traits such as pagination behavior, rate limits, or data freshness. It is consistent with the annotations, so no contradiction.

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 concise: a one-sentence summary followed by a clear, structured Args block. Every piece of information is useful and not redundant with the schema, making it well-organized and appropriately sized.

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?

The description covers the return values and parameter semantics well. It lacks a few details, such as whether checkin and checkout must be used together or how results are ordered, but given the simple search use case and no output schema, it is sufficiently complete for an agent to invoke the tool 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 Args section fully explains all four parameters with format, optionality, and defaults. Schema description coverage is 0%, so the description carries the full burden, and it excels by providing concrete examples like 'Paris, France' and date format YYYY-MM-DD.

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 'Search Airbnb listings by location' and specifies what it returns (prices, ratings, amenities, host info). This is specific to the Airbnb resource and naturally distinguishes it from sibling tools like search_hotels and search_tripadvisor.

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 gives clear context for usage: it searches Airbnb by location. It does not explicitly mention when not to use it or point to alternatives, but the Airbnb-specific naming implies the appropriate use case. No misleading guidance is present.

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