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

Annotations only declare readOnlyHint=true, but the description adds substantive behavior: the no-filter default of returning only upcoming bookings, the required bookings-personal / bookings-financial scopes for guest and invoice data, and the filter semantics. It does not discuss pagination (left to the schema) or result size, so it is strong rather than exhaustive.

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?

Dense but front-loaded: the filterable dimensions come first, then the no-filter default, then the shortcut meanings, then scopes. Every sentence carries information, though the middle sentence packs four unrelated facts together and could be split for readability.

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 24-parameter, zero-required read tool with no output schema, the description supplies the essential missing context: default result scope, filter shortcuts, and permission scopes. Pagination behavior is delegated to the schema and no return shape is given, but that is acceptable given the schema's page parameter documents nextPageExists.

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 83%, so the baseline is 3; the description goes beyond it by decoding the otherwise undocumented `filter` enum values (arrivals/departures/new/current), clarifying what searchString matches, and tying includeGuests/includeInvoiceItems to their required scopes. The date-range parameter pairs are left to the schema.

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 precise verb (Search) and resource (bookings) plus the full set of filterable dimensions, so the agent immediately knows this is the listing/search endpoint rather than a create/get/update sibling. It also maps to the underlying API operation (GET /bookings), anchoring intent.

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?

Gives clear when-to-use context via the filter shortcuts (arrivals/departures/new/current) and explains the default behavior with no filters (upcoming bookings only), which is exactly the guidance needed to pick a call shape. It stops short of naming sibling alternatives such as get_booking for single-record fetches.

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