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

The description correctly implies a read-only lookup of bookable offerings with a link to book externally, which is consistent with readOnlyHint and idempotentHint. It does not delve into behavioral details like response format, pagination, or availability, but annotations reduce the burden here.

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, front-loaded sentence conveys the resource, the data returned, and the port context. No filler or repetition of the title.

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-only tool with no output schema, the description gives enough context about what the user gets: price, duration, rating, and link. It could be more explicit about the response shape or result limits, but the simplicity of the tool keeps gaps minor.

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 documentation covers the single 'port' parameter fully with format and example, and the description reinforces that it is a cruise port. Since schema coverage is 100%, the description does not need to compensate much for parameter 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 clearly states the tool retrieves shore excursions and resort day passes for a cruise port, and lists meaningful result attributes. It is distinct from sibling tools like getPortGuide or searchCruises, though it doesn't explicitly contrast with them.

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 context is clear: use it when excursion or day-pass options for a specific port are needed. However, there is no explicit when-not-to-use guidance or mention of sibling alternatives such as getPortGuide for general port information.

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