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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the safety profile is covered. The description adds genuinely useful non-schema context: pricing is an all-inclusive stay total, requires both dates, and works without an API key but only with cached prices.

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?

Front-loaded with the core purpose, then the returned contents, then the pricing caveat. Content is tight with no filler, though the multi-line indentation and trailing whitespace make the raw text slightly awkward.

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 carries the burden of describing returns and does so by listing the profile sections. The pricing/auth caveat is included. Minor gap: no indication of response size, pagination, or image/media limits.

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 baseline is 3. The description reinforces the check_in/check_out coupling for pricing, but the schema already states 'Prices need check_in and check_out', so it adds little beyond the structured fields.

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+resource ('Full profile of one hotel by its hotel_id') and enumerates exactly what the profile contains (description, amenities, images, rooms, reviews, insights). It also anchors the tool against the sibling search_hotels by naming it as the source of hotel_id.

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?

Clear context: it must be called with a hotel_id obtained from search_hotels, and the description explains the conditional pricing behavior (price only when both check_in and check_out are supplied). It does not, however, explicitly say when to prefer chat_about_hotels or search_hotels instead.

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