Get similar accommodations

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

Annotations already declare readOnly, idempotent, open-world, non-destructive behavior, so safety is covered. The description adds nothing beyond that: it does not say how similarity is determined, how many results come back, whether ordering or ranking applies, or whether the source listing itself is excluded. For an open-world recommendation endpoint, these are meaningful gaps.

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?

A single front-loaded sentence with no filler or repetition. Brevity is appropriate in form, though the same sentence is too thin to carry much information.

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, no parameter documentation, and a low-complexity surface, the description should explain what a 'similar stay' result looks like and the semantics of the seed id. It says neither, leaving an agent that must act on the returned list without knowing its shape or relationship to the input.

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 description coverage is 0%, so the description must carry parameter meaning, and it only restates the name as 'house id'. It does not clarify that the integer is an accommodation identifier, how to obtain one (e.g., via sh_search_accommodations), or what happens with an unknown id.

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 verb ('List') and resource ('similar stays') tied to a 'house id', so the general intent is retrievable. However 'similar' is undefined and the phrasing 'stays' vs 'accommodations' leaves it ambiguous whether items are accommodations or availability records, which matters given siblings like sh_get_accommodation and sh_search_accommodations.

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?

There is no guidance on when to call this rather than sh_get_accommodation, sh_search_accommodations, or sh_check_availability. A caller cannot infer from the description whether this is for recommendation-style discovery or for expanding a known listing.

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