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

Beyond annotations, it discloses that the call makes a fresh on-demand search, that suggestions are not verified to fit time ashore, and that there is no live availability. It also explains that users can change filters and open Viator booking links, and warns not to fetch details for every result. This is strong behavioral context for an interactive, read-only browser tool.

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 front-loaded with the core action and follows with useful constraints. Some UI workflow detail, such as users changing ports, dates, keywords and pages, is helpful but slightly verbose for a tool description.

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 complex interactive tool, it covers when to call, filter behavior, safety warnings, and user-facing interactions. However, with no output schema, it does not describe the returned data shape, and it does not state where to obtain a supported portId.

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?

With 0% schema description coverage, the description compensates for most parameters: it explains portId omission and supported local values, optional visit date, and activity keywords q. The page parameter is only implied through 'pages', so pagination semantics are not fully explicit.

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?

It uses a specific verb and resource: 'Open ONE interactive port-experience browser' for excursions, tours or activities. This clearly distinguishes the presentation/browser action from data-fetching siblings like find_port_excursions and get_excursion, and the first sentence is front-loaded.

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?

It gives clear usage conditions: use only on an experience request, never automatically for every cruise search, and omit portId to let the user choose a port without calling Viator. It also says not to fetch details for every result. It does not explicitly name sibling alternatives such as find_port_excursions or get_excursion, so it falls short of the highest tier.

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