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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint=false), so the description earns credit for going beyond them: it discloses ordering (newest charter first), the meaning of the empty result set, and the lifecycle semantics of status values including the hold_expires_at lapse rule. It does not mention pagination or result-size limits, which is the remaining gap.

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?

Four sentences, front-loaded with scope and ordering before the status vocabulary and the read-only caveat. The status-definition sentence is dense but each clause carries distinct domain meaning; nothing reads as 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?

With no output schema, the description compensates well by describing what each row contains (guest price, discounts, operator payout, payout currency) plus ordering and the empty case. Pagination and total-count behavior are the only meaningful omissions.

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 100% and the single boat_id parameter is documented there as 'Optional: one boat only.' The description adds nothing about that filter, so the schema carries the full burden — 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?

The description states the resource and scope precisely: 'Every booking on the operator's boats, newest charter first.' That is far more specific than a bare list tool, but it never distinguishes itself from the sibling get_booking, which retrieves a single booking — an agent must infer the split from the tool names alone.

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?

'Read-only: bookings are handled on the dashboard' signals when this tool is appropriate (inspection) and when it is not (booking management), and the empty-list note tells the agent what an empty result means. It stops short of naming get_booking as the alternative for a single booking, so routing is implied rather than explicit.

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