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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is fully covered. The description adds genuinely useful behavior: amenities and media are omitted by default, and no live availability or party total is guaranteed. That is real value, but it does not disclose response shape or pagination/limits, keeping it at a solid 3-4 borderline; the default-omission semantics push it to 3.

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 action and resource, then the constraints. Four short sentences with no filler, though the fragment style ('Research only; no widget.') is terse enough that it reads as telegraphic rather than fully polished.

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 an output schema present, the description needn't explain return values, and rich annotations cover the safety profile. It closes the remaining gaps an agent would care about (default-omitted content, no guaranteed live availability), leaving only minor omissions around limits or error behavior.

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 every parameter including offerId provenance, cabinClass normalization, and the includeMedia/includeAmenities defaults is already documented in the schema. The description only restates the opt-in behavior for amenities/media, adding no syntax or provenance detail 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 and resource ('Explore a CruiseHops sailing page') and enumerates what it returns: itinerary, cabin fares, price-history context, links. It implicitly contrasts with a widget-based sibling via 'Research only; no widget', but never names compare_sailings or get_price_history, so sibling differentiation is partial.

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?

'Research only; no widget' establishes a clear usage context and rules out the presentation path, and the sentence on amenities/media tells the agent when to enable optional includes. It stops short of naming explicit alternatives for overlapping needs like price history or comparison.

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