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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds the useful trait that the returned data is static (cached catalog-style content), but says nothing about error behavior for invalid ids, latency, 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?

A single sentence with the payload fields front-loaded and the provenance constraint appended. No filler or redundancy.

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?

For a one-parameter read tool with annotations and no output schema, this is nearly complete: it names the return fields so the agent knows what it gets. It stops short only on failure modes and the search-then-detail workflow being spelled out explicitly.

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 coverage is 100% and the single parameter is already documented as 'Hotel id from search_hotels'. The description repeats the same provenance rather than adding format, validation, or failure behavior, so the schema carries the weight.

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 (get) and resource (hotel details), and enumerates what is returned: description, amenities, photos, address. It also anchors the tool in the workflow by noting the id comes from search_hotels, which distinguishes it from search_hotels and get_room_rates_for_hotel without naming them explicitly.

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 agent must infer it should call search_hotels first, then this tool, and that rate information belongs to get_room_rates_for_hotel. The word 'static' hints at the boundary with the rates sibling, but no explicit when/when-not guidance or alternative is given.

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