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

Annotations already cover readOnly, idempotent, and non-destructive traits, so the bar is lower. The description adds real value on top: it discloses the error behavior ('answers that the dates are not available when they are taken') and clarifies the output is page-accurate ('as its page shows it') and side-effect free ('not a booking').

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?

Three tight sentences with the core purpose front-loaded, followed by the availability caveat and the booking disclaimer. No filler, though it could be trimmed slightly since the mode names duplicate schema descriptions.

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?

With no output schema, the description compensates by characterizing the return as the total price shown on the listing page and by noting the unavailable-dates response. It omits pagination/format specifics and explicit sibling routing, but for a read-only quote tool the essentials are covered.

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 both parameter groups are already documented in the schema, including the 'booked by nights' vs 'booked by time slots' distinction. The description restates those groupings but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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?

States a specific verb+resource: computes the total price of a stay or time slot at one listing. The two input modes (check_in/check_out vs date/start_time/end_time) are spelled out, though siblings aren't named explicitly. Clear enough to distinguish from get_booking_link via the 'not a booking' note.

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?

Implies usage through the two mode descriptions and the 'a quote is not a booking' clarification, which steers an agent away from booking flows. However, it never states when to reach for get_quote versus get_listing or get_booking_link, so the routing guidance is only implied.

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