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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description usefully adds that results are 'undated' (no availability/pricing) and that home lookups require a reference from search results. It does not say what happens with an ambiguous hotelName or a name that fails to match.

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 sentences, front-loaded with the core behavior and no padding. The 'propertyRef' vs 'propertyId' terminology drift is the one spot where wording costs clarity rather than saving space.

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?

No output schema exists, and the description only gestures at the return payload ('facts, photos, and amenities') without indicating structure or currency handling. Combined with the unexplained currency parameter and the propertyRef ambiguity, an agent has enough to attempt the call but not enough to predict the result.

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 0%, so the description must carry the load. It explains hotelName, propertyId, and destination semantics well, but currency is never mentioned, and the description references a 'propertyRef' that does not exist in the input schema (the parameter is propertyId), which risks confusing the agent about which field to send.

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 and resource: 'Return undated hotel or motel facts, photos, and amenities.' The word 'undated' plus the fact/photo/amenity scope implicitly separates it from get_hotel_offers, and the closing sentence about furnished homes separates it from get_home_details, though neither sibling is named explicitly.

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?

Gives clear lookup-mode guidance: use propertyId from a search result, or hotelName directly, with optional destination to narrow a name match. It also states a hard constraint (furnished homes cannot be queried by name alone). It stops short of explicitly routing to get_hotel_offers for pricing or to search_stays for discovery.

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