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 states the tool returns blocked date ranges but does not clarify whether the returned ranges are filtered by the given from/to dates, how inclusive the boundaries are, or if locale affects output. Basic read-only nature is implied but not explicitly confirmed.

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 two concise sentences with no filler. It is front-loaded with the action ('Check availability') and delivers the key information efficiently. Every word earns its place.

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 is short and leaves gaps: no output schema exists, and the description only vaguely says 'Returns blocked date ranges.' It does not specify the structure of the output, whether the date range parameters filter the results, or if there are any special behaviors. For a moderate-complexity tool, more detail would improve completeness, though it is not severely inadequate.

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 input schema covers 75% of parameters with descriptions (listing_id, from_date, to_date), and the locale has an enum but no description. The tool description adds little beyond the schema, merely reinforcing 'specific property' and 'availability'. Since schema coverage is high, the baseline of 3 applies; the description does not significantly enhance parameter understanding.

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 function: 'Check availability/booking dates for a specific property.' It uses a specific verb ('check') and resource ('availability/booking dates'), and notes the output ('Returns blocked date ranges'). This distinguishes it from siblings like get_listing_detail or search_listings, which serve different purposes.

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 the usage context: you use this when you have a specific property and want to know its booked/blocked date ranges. However, it does not explicitly mention when not to use it or point to alternatives. The context is clear but exclusions are absent, which places it at a 4 rather than 5.

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