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

Annotations already declare readOnly/openWorld/non-destructive, so the bar is lower; the description adds ordering (most recent first), the returned fields, and an explicit auth requirement (Cotlet API key with app access), which is genuine context beyond the annotations. It stops short of pagination/rate-limit behavior.

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?

Front-loaded and efficient, with the core purpose in the first sentence and scoping/param hints afterwards. Slight redundancy: the booking reference is stated twice across the opening sentences.

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 no output schema, the description carries the return-value burden and does so by naming the fields returned and the ordering. Auth is covered; pagination mechanics rely entirely on the cursor schema entry, which is adequate for this list tool.

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%, so the schema already documents limit, cursor, and unread_only. The description restates the unread_only meaning ('only what needs an answer') but adds no syntax or defaults beyond the schema, making the baseline 3 appropriate.

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 clear verb and resource: routes to the Messages conversations and enumerates what each entry contains (traveler, booking reference, unread count, last message). An agent can distinguish it from getyourguide_reply_to_message, though the sibling is not named explicitly.

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?

Offers one practical cue (set unread_only to surface what needs an answer) but gives no when-to-use vs alternative framing and never references the reply_to_message sibling or prerequisites for reading. Usage is implied rather than instructed.

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