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

Annotations already declare readOnly, idempotent, non-destructive, openWorld behavior, so the safety profile is covered. The description adds genuine value by enumerating the returned payload (amenities, images, location, ratings, chain/star metadata), which matters since no output schema exists. It does not mention error cases (e.g. unknown hotelId) or rate limits.

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?

The markdown scaffolding is heavy and much of it is redundant: 'What You Get' largely repeats the Overview's list of descriptions/amenities/images/location/ratings, and the four 'When to Use' bullets say essentially the same thing. The signal could be conveyed in a third of the text.

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 usefully compensates by listing returned fields, and it covers the required hotelId call path. However, it says nothing about the three optional parameters' effect (language, timeout, advancedAccessibilityOnly) or failure behavior, so it is adequate rather than complete.

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 100%, so the schema already documents all four parameters including language, timeout, and advancedAccessibilityOnly. The description only references hotelId as a query parameter and adds no format or semantics beyond the schema, fitting the baseline of 3.

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 Overview states a specific verb+resource: 'Get comprehensive details about a specific hotel.' It clearly distinguishes a by-ID detail lookup from list/search siblings like get_data_hotels and get_data_hotel_search, but it never names those siblings explicitly, leaving the differentiation to inference.

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?

The 'When to Use' section lists four scenarios, but they are near-identical restatements ('hotel detail pages', 'hotel profiles', 'content display') rather than decision criteria. No alternative tool is named and there is no 'when not to use' guidance, so usage is only implied.

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