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

Annotations already establish read-only and closed-world behavior. The description adds useful scope about current discounted availability and the model-level return fields, but does not cover pagination, limits, result ordering, or other behavioral traits beyond the 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?

It is a single front-loaded sentence with the key scope up front. The long list of return fields is somewhat dense, especially since an output schema exists, but it remains readable and waste is limited.

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?

With an output schema present, return values do not need full explanation, and the description covers the main filters. However, it omits the limit/pagination behavior and does not fully clarify how destination filtering maps to the country parameter.

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 description coverage is low (25%), and the description compensates partially by naming boat type, destination and minimum cabins as filters. It does not explain the country/destination enum semantics beyond 'destination', does not clarify boat type values, and leaves the limit parameter undocumented.

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 states a specific resource (yacht models) and scope (models that have discounted weeks now), which clearly separates it from get_yacht_model (single model) and search_deals (deals). It does not explicitly name or contrast sibling tools, keeping it just short of a 5.

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 says to filter by boat type, destination and minimum cabins, which implies usage for browsing discounted models. However, it gives no explicit when-to-use vs alternatives (e.g., search_deals or get_yacht_model) or exclusions.

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