Get accommodation

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered structurally. The description adds genuinely useful context beyond that — that prices are denominated in Toman and that booking happens externally via listing_url on shab.ir — but says nothing about what the returned detail set contains or whether the record can be missing.

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 very short sentences with the core purpose front-loaded; nothing is padded. The booking note is marginally tangential to retrieval but earns its place by telling the agent where the transaction actually happens.

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?

This is a simple single-parameter read tool whose annotations and schema are fully specified, so little is required. However, with no output schema, the description leaves "details" undefined — an agent cannot anticipate which fields come back, and the currency note is the only hint about return content.

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 100% for the single parameter ("Shab house id."), so the baseline is 3. The description does not add any meaning to accommodation_id, nor explain how to obtain a valid 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?

"Get one stay's details" pairs a specific verb (get) with a singular resource (one stay/accommodation), which distinguishes it from the sibling search, photos, and reviews tools. The wording "stay" instead of "accommodation" is slightly loose but still unambiguous in context.

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 explicit when-to-use guidance: nothing says to call this after a search returns an id, nor when to prefer it over sh_get_accommodation_photos, sh_get_accommodation_reviews, or sh_get_similar_accommodations. Only the word "one" implies single-item retrieval rather than listing.

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