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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety and idempotency profile is covered. The description adds the content scope (what fields come back) but nothing about auth requirements, rate limits, or whether a missing identifier errors versus returns null.

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 front-loaded sentence enumerating the returned payload with zero filler. Every clause adds information an agent can use.

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 correctly compensates by enumerating the returned fields (description, amenities, times, policies, rating, review summary, room types, photos, address). The remaining gap is the lack of sibling routing guidance and any note on the include_rooms toggle.

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 description coverage is 0% for both parameters, so the description has to carry the load; it does clarify that hotel_identifier accepts an id or a slug, which is genuinely useful. However, include_rooms (default true) is never explained — the mention of 'room types' among returned fields only weakly implies its effect.

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 ('Full details for one hotel') and narrows retrieval to 'by id or slug', which separates it from the search_* siblings that take queries. It does not directly name which sibling to prefer, but the single-entity scope is unambiguous.

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: the description makes clear this is a single-hotel lookup keyed by identifier, but it never states when to reach for this instead of search_hotels, get_nearby_hotels, compare_hotels, or get_live_rates. No prerequisites or exclusions are given.

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