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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavior beyond them: capped at 8 matches, a per-area "Other hotel or villa" fallback id when nothing matches, and 199 properties across named regions. It also discloses the out-of-scope regions handled by email instead, which prevents a dead-end call.

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?

Four sentences, each carrying distinct load: what is searched, what comes back, coverage extent, and where the tool does not apply. The return-shape and fallback id lead before the regional caveat, so the most decision-relevant facts are front-loaded.

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 compensates by stating result count, return id semantics, and the no-match fallback. For a one-parameter read with full annotation coverage, nothing an agent needs in order to call it correctly or interpret the response is missing.

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% and the single query parameter is fully described there, so the schema does the heavy lifting. The description adds only indirect signal about input tolerance (town names as well as property names, implied by the area/fallback behavior), which is a marginal gain over the existing example-bearing schema.

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 ("Find hotels and villas"), scopes it geographically to properties served from MBJ, and ties the output to a sibling ("the id to use in get_transfer_quote"). An agent can distinguish this lookup step from booking/quote/pricing siblings without opening any schema.

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 routes the agent: use this to obtain the id consumed by get_transfer_quote, and use email quoting for Kingston, Port Antonio and Mandeville. It gives a clear when-to-use context and a regional exclusion, but never names the other siblings (check_transfer_timing, get_booking_terms) or says those should be called after this one.

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