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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint, so 'Read-only' is mildly redundant, but the description adds genuinely useful behavioral detail: deposits are 'held by the property' and taxes and cancellation policy are part of the payload. No permission or failure-mode context is given, which keeps it below a 5.

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?

Front-loads the mode and the one-line purpose before the field inventory. The enumeration is long but earns its place because there is no output schema to describe the response, and there is no filler.

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 listing the returned fields (type, photos, amenities, house rules, rooms/units, fees, taxes, cancellation, deposit), and it covers the single input's source. Missing only minor operational detail such as error behavior for an unknown slug.

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% (pattern plus example), so the baseline is 3, but the description adds origin semantics for the slug value — it comes from search_stays or a Bookd link — which the schema does not convey.

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 (get) and a precisely scoped resource (one Bookd property, by slug), then enumerates the payload contents. It is clearly distinguishable from sibling search_stays, whose results feed the slug input.

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?

Explicitly tells the agent where the slug originates ('from search_stays or a Bookd link'), which establishes the natural call sequence. It does not state when not to use it or name alternatives for other lookups, but the entry condition is unambiguous.

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