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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the bar is lower. The description usefully adds the required-parameter-pair rule and the 31-day span cap, but says nothing about result volume, pagination behavior, or what 'expand' actually returns.

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?

Two tight sentences plus the endpoint reference, with the hard requirement front-loaded rather than buried after the optional features. Every clause carries information.

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 read-only list tool with no output schema and 11 fully documented parameters, the description covers the essential invocation constraints. It is nonetheless silent on return shape and on how paging interacts with the required search windows.

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%, so the per-parameter baseline is 3. The description earns above baseline by surfacing the cross-parameter constraint (startTime+endTime or lastUpdatedStartTime+lastUpdatedEndTime, at least one pair, max 31 days) that no individual schema field expresses.

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 specific verb and resource plus the two filtering modes (start-time window vs. last-changed window), which is far more informative than the title 'List bookings'. An agent can distinguish this bulk/range listing from bookeo_get_booking and bookeo_list_customer_bookings without opening a schema.

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?

Explicitly states the gating rule — 'at least one pair is required, each spanning at most 31 days' — which is exactly the context needed to call it successfully. It does not, however, name when to prefer it over siblings such as bookeo_list_customer_bookings or bookeo_search_matching_slots.

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