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

Beyond readOnlyHint=true, the description discloses the breadth of the returned listing and the conditional inclusion of total price and availability when dates are supplied. It does not explain whether both dates are required together, how unavailability is represented, or likely errors, which are relevant gaps without an output schema.

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 single sentence is front-loaded with “Full listing of one stay” and uses a dense but relevant field list without filler. Its final conditional clause efficiently connects the optional dates to pricing and availability behavior.

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?

For a read-only, four-parameter detail tool, the description provides a useful response overview and the main conditional behavior, which is especially valuable because there is no output schema. It remains incomplete on slug provenance, whether the dates must be paired, and explicit routing among the sibling tools.

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 schema already documents locale and the YYYY-MM-DD date formats, while the description adds that dates activate pricing and availability information. It does not explain what a slug is or where to obtain one, and “with dates” only implies rather than states that checkIn and checkOut should be supplied together.

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?

“Full listing of one stay” clearly identifies single-rental detail retrieval and enumerates the information returned, making it narrower than a general search. It does not explicitly contrast itself with search_stays or get_availability, so sibling differentiation remains implicit.

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 phrase “with dates” gives a concrete condition: supply stay dates when total price and availability are needed in addition to listing details. However, it does not direct availability-only requests to get_availability, discovery to search_stays, or booking to prepare_booking.

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