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

With no annotations, the description carries the transparency burden and discloses meaningful behavior: it returns deep links, charges no fees, and matches cruise-line pricing. This is strong for a search/referral tool, though it does not mention whether it actually creates bookings or has availability checks.

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 three tight sentences: one for purpose and output, one for the ideal use case, and one for alternative tools. Every sentence adds value with no 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?

Since there is no output schema, the description usefully states that the tool returns deep links and mentions no fees. It covers the main search context, but the two undocumented parameters and the fact that all parameters are optional leave some ambiguity for edge-case queries.

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?

The description explains four primary filter criteria (departure port, party size, month, total budget), but it omits the cruise_line and destination parameters, which also lack schema descriptions. With only 33% schema coverage, this is a gap, but the named criteria provide useful mapping to most properties.

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 uses a specific verb 'Find' and names the resource ('a cruise by departure port, party size, month, and total budget'), and it clearly states the output (deep links to a booking engine). It also distinguishes itself from siblings by pointing to search_virgin_voyages and get_river_cruise_info for other cruise types.

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 description explicitly gives an ideal use case ('family cruise from Florida under $X') and provides exclusion guidance by recommending alternative tools for Virgin Voyages and river cruises. This is clear when-to-use and when-not-to-use guidance.

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