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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety and repeatability are covered. The description adds genuinely new context — that each entry carries a capability flag telling the agent whether booking-and-paying or only preparing a reservation is possible — which is useful behavioral information not derivable from the annotations. It says nothing about how the list is ordered, its size, or pagination, which matters for an openWorld list.

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?

One well-formed sentence with the resource front-loaded and the payload details trailing in a compact relative clause. No waste, though the parenthetical about booking-and-payment vs. prepare-only is dense enough that it reads slightly faster than it parses.

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 bears the burden of saying what comes back, and it does: identifier, address, and per-hotel action capability. For a zero-parameter read tool with strong annotations that is close to sufficient; missing volume/ordering hints keep it from a 5.

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?

Zero parameters, so the baseline is 4 by rule. The description correctly signals a no-input listing and additionally names the identifier field (property_id) an agent will need for follow-up calls, a small bonus beyond the empty 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 resource (the hotels sold by this server) and enumerates the payload: property_id, address, and per-hotel agent capabilities (book+pay vs. prepare-only). That is far more than a name restatement. It does not explicitly contrast itself with get_property_details, which an agent might confuse it with for single-hotel lookups.

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 implied rather than stated: the capability clause signals it as a discovery step (find out what you can do at each hotel), but there is no explicit when-to-use/when-not or pointer to get_property_details for detail-level or get_rooftop_availability for availability. The agent must infer the routing.

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