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

Annotations already establish readOnlyHint=true, and the description adds real behavioral constraints beyond that: the mandatory time-pair rule, the 31-day cap, and the fact that canceled bookings are excluded unless requested. It stops short of describing pagination behavior or response shape, but the safety profile is already covered by 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?

A single dense opening sentence front-loads the required constraint and filters, followed by a short API pointer. There is no filler or repetition of schema details.

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 and 11 parameters, the description covers the essential call semantics: the mandatory time-pair rule, the 31-day limit, optional filters, and expansion flags. Return format and pagination behavior are left to the schema's pageNavigationToken description, which is acceptable but not fully closed.

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 baseline is 3, but the description contributes a rule the schema never states: that at least one of the two time-parameter pairs is mandatory, and how startTime/endTime relate to lastUpdatedStartTime/lastUpdatedEndTime. It also confirms productId/canceled/expand act as optional filters.

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 verb and resource ('List bookings') and immediately scopes it by the two supported query modes (start time pair and/or last-change pair), plus the optional filters. That is enough to separate it from single-booking siblings like bookeo_get_booking and from the more narrowly scoped bookeo_list_customer_bookings.

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 gives concrete preconditions: at least one time pair is required and each pair may span at most 31 days. It does not, however, name an alternative tool or say when to prefer bookeo_get_booking or bookeo_list_customer_bookings over this list call, so usage context is clear but not fully routed.

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