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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds one useful piece of context beyond that: the data is 'as stated in the official property listing', signalling an authoritative, static source rather than a live or negotiated value. It does not address whether policies are property-specific or what happens when a policy is unstated.

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 sentence with no filler; the highest-value topics (check-in/check-out, minimum age, maximum guests) are front-loaded and the list is a legitimate topic index rather than padding. It is dense and comma-heavy, which slightly hurts scanability, but nothing is redundant.

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 zero parameters, an output schema present, and full annotation coverage, the description only needs to convey scope — which it does thoroughly. The remaining gap is behavioral edge cases (what an agent should do if a requested policy is not listed), which is minor for a static read-only lookup.

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 tool takes zero parameters, so the baseline is 4 and there is no parameter semantics to explain. The description correctly spends none of its length on input discussion.

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?

The description enumerates the exact policy topics returned (check-in/out times, min age, pets, smoking, quiet hours, parking, taxes, quote and cancellation mechanics), which makes the resource unmistakable and separates it from siblings like get_amenities or get_property_overview. It omits an explicit verb such as 'returns' or 'retrieves', relying on the name to carry the action, but the content scope is specific enough for an agent to select it confidently.

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?

Usage is only implied: an agent can infer it should call this when a guest asks about stay rules, taxes, or cancellation terms. There is no explicit when-to-use statement, no mention of how this differs from get_property_overview or get_quote (both plausible overlaps for taxes/quote questions), and no exclusions.

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