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

Annotations declare readOnlyHint=true and openWorldHint=false, covering the safety profile. The description adds value beyond this by disclosing that prices carry a read date, that some grades may have no listed price, and that port recommendations include verified sellers with booking pages. However, it doesn't clarify the response shape or any 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 description is a single long, comma-spliced sentence enumerating many return fields. It is front-loaded with 'Everything about one sailing' but the sprawling list of outputs makes it somewhat hard to parse; tightening would improve it.

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 read-only detail tool with no output schema, the description does a good job enumerating what is returned. However, it omits identification requirements (must supply url or sailing_id), what happens if neither is provided, and any pagination or size caveats.

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%, so baseline is 3. The cabin enum and its omission-default behavior ('quote balcony where sold, else the next grade') are documented in the schema itself, not the description, so the description adds little parameter-level meaning.

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 description names the specific resource (one sailing) and enumerates its contents in detail: itinerary, prices, history, alternatives, ports. It's clearly distinct from search_cruises and compare_cruise_lines, though it doesn't explicitly name a sibling to differentiate.

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?

No when-to-use guidance or alternatives named. The agent must infer that this is for retrieving full details of a single already-identified sailing versus searching. The schema (url/sailing_id) implies identification-first, but the description doesn't say so.

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