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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only the notion that results are curated and well-rated, which is mild behavioral context. It says nothing about result count, ordering, or what happens when the limit is exceeded.

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 short sentence with no filler and no redundancy. It is appropriately sized for a one-parameter read tool, though it is a sentence fragment rather than a front-loaded statement of action and scope.

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 does not describe the return shape, the number of hotels returned, or how the limit interacts with the curated set. For a discovery tool competing with several hotel-returning siblings, that leaves the agent guessing about both behavior and output.

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?

There is one parameter (limit, default 20) with 0% schema description coverage, so the description carries the full burden — and it never mentions limit, its default, or whether it caps the returned set. With a single undocumented param the description should have compensated, and it does not.

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 names the resource ('hotels') and a qualifier ('featured/curated, well-rated'), so an agent can guess it returns a curated hotel list. But it is a noun phrase with no verb ('returns', 'lists') and no differentiation from siblings like search_hotels or get_nearby_hotels, which also return hotels. Purpose is inferable but not stated.

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 versus search_hotels, get_nearby_hotels, compare_hotels, or get_hotel_details. 'Curated' hints at editorial selection rather than query-driven search, but the agent is left to infer that distinction. No exclusions or prerequisites are given.

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