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

Annotations already provide readOnlyHint=true, idempotentHint=true, and openWorldHint=false, covering the basic safety profile. The description adds output field details and the 'biggest' qualifier, but does not disclose any additional behavioral traits such as result limits, data source, or pagination. It does not contradict annotations.

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 concise sentence that front-loads the core purpose and then lists the returned fields. Every word adds value, with no filler or 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?

For a simple tool with one optional parameter and no output schema, the description should explain the parameter and result semantics. It lists return fields but omits any explanation of 'limit' and does not clarify whether results cover all cruises or a subset. An agent cannot confidently invoke the tool correctly without this missing context.

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 only parameter, 'limit', has a schema definition with minimum and maximum but no description. Schema description coverage is 0%, and the tool description does not mention the parameter at all, leaving its purpose and effect on results completely unexplained. The description fails to compensate for the schema gap.

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 returns the biggest current cruise price drops and lists the specific fields included (cabin type, prices, percent dropped, sail date, booking link). It implicitly differentiates from siblings like getPriceHistory by emphasizing 'current', but it does not explicitly name alternatives.

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 tool's purpose implies it should be used when current price drops are needed, but the description gives no explicit guidance on when to prefer it over related tools like getPriceHistory or searchCruises. There is no mention of when not to use it or alternative conditions.

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