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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real content context beyond that: results are editioned by sailing dates, include PDFs plus the cruise line's own source, cabin grades, and editorial noise/avoid notes with page links. It omits whether coverage can be missing for some ships, which keeps it from a 5.

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?

One sentence, front-loaded with the scoping constraint, and every clause names actual return content. It is somewhat run-on with stacked parentheticals ('noise from pools, theaters, galleys above or below'), which slightly hurts scannability but nothing is filler.

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?

A single-parameter read tool with no output schema, so the description carries the burden of describing returns, which it does thoroughly (editions, PDFs, source, grades, avoid notes, links). Only the edge case of missing deck-plan data for a given ship is unaddressed.

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% and the single 'ship' parameter is documented as a slug obtainable from list_cruise_ships. The description adds no format or resolution detail beyond that, so the baseline 3 applies.

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 resource and scope: 'For one cruise ship: its deck plan editions by sailing dates, with the PDF and the cruise line's own source, the cabin grades, and ... notes on quieter cabins and cabins to check or avoid.' An agent can immediately distinguish this from get_cruise_ship (general ship data) or get_ship_metrics without opening a schema.

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 scope phrase 'For one cruise ship' implies it is a single-entity lookup, and the schema points to list_cruise_ships for the slug, but the description never says when to pick this over get_cruise_ship or top_cruise_ships, nor any exclusion conditions. Usage is inferable rather than stated.

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