list_bookings

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

With no annotations, the description carries the full burden. It discloses a key behavioral trait: the endpoint always uses a time bound (since_utc) and is not bound by stay dates, which is critical for correct usage. It does not mention pagination or rate limits, but output schema exists.

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?

Three short sentences, front-loaded with 'List bookings.' Each sentence earns its place: the first states purpose, the second explains the time-bound behavior, and the third gives a clear filtering instruction. No unnecessary information or repetition.

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 an 8-parameter list tool with output schema and no annotations, the description focuses on the most important nuance that wouldn't be obvious from the schema alone. The parameter descriptions cover defaults and filters, so the description doesn't need to restate them. Minor gaps exist around pagination and max_items, but these are documented in the schema.

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 baseline is 3. The description adds meaning by explaining the relationship between since_utc and arrival filters: since_utc is the actual API bound, while arrival_start/arrival_end are client-side narrowing. This clarifies the intended usage of these parameters beyond their schema descriptions.

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 opens with 'List bookings.' which clearly identifies the verb and resource. It further explains the scope (bookings created or changed since a UTC time), distinguishing it from singular and other resource-specific list tools.

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 provides clear context that the endpoint is bounded by since_utc rather than stay dates, and explicitly instructs to use arrival_start/arrival_end to narrow by stay window client-side. It does not explicitly reference alternatives like get_booking, but the guidance is clear and actionable.

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