Search bookings

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it discloses the return shape (counts by status and page plus a compact list with booker name and email) and the effect of raw=true, which is valuable given there is no output schema.

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, no filler. The scope (time range) and filters come first, followed by return shape and the raw toggle, so the highest-value information is front-loaded.

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 10-parameter read tool with no output schema, the description covers the essential call semantics and return shape. Pagination controls (direction, fromBookingId, pageSize) are left to the schema, which is acceptable since they are documented there, but the description could note continuation behavior.

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 80%, so most parameters are documented. The description goes beyond by explaining what searchText actually matches against (booker name/email, title, booking ref) and what raw=true does, which compensates for the undocumented raw flag in 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 specific verb (search) plus resource (bookings) and enumerates the filter dimensions: time range, status, booking page, and text. An agent can distinguish it from get_booking or list_upcoming_bookings by the presence of multi-filter search, though no sibling is 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?

The description implies usage through 'optionally by status, booking page, or text' and the required time range, but it never states when to prefer this over list_upcoming_bookings or get_booking, nor any exclusions or prerequisites. Usage is inferable rather than prescribed.

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