List upcoming bookings

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds real context beyond them: cancelled bookings are excluded, results are ordered soonest-first, and each row carries the booker name and email. It still says nothing about pagination or result-size limits on a potentially open-ended window.

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 sentence with no filler, front-loading the operation and layering scope, ordering, and returned fields in a natural reading order.

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, the description usefully names the key returned fields (booker name and email), and annotations cover the read-only profile. The gap is the undocumented bookingPageIds parameter and the absence of any note on result volume for larger day 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 coverage is 50%: 'days' is fully documented by the schema (default 7, range 1-90) and echoed by the description's 'next N days', but bookingPageIds has no description anywhere. The description also fails to clarify whether supplying bookingPageIds narrows the list to those pages or is a scope requirement, so it does not compensate for the coverage gap. Baseline 3 applies.

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 gives a specific verb and resource (list upcoming bookings) plus meaningful scope: not cancelled, next N days, soonest first. That functionally separates it from search_bookings and get_booking, though it never names a sibling 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?

Usage is implied by the 'upcoming, not cancelled, next N days' framing, which tells the agent this is a time-window roll-up rather than a query tool. There is no explicit when-to-use/when-not guidance and no routing to search_bookings or booking_report for other needs.

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