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

Annotations already mark this tool as read-only and non-destructive, and the description adds meaningful behavioral context beyond that: bookings are scoped to the current team, sorted earliest first, tied to a lead owner and source quiz, and attendee names/emails come back masked. These details are not inferable from the annotations alone.

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?

The description is compact and front-loaded with the core purpose, then adds distinct, practical details: item shape, filtering, a typical approval-queue workflow, and the masked attendee caveat. There is no filler or redundant wording.

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 listing tool with 9 optional, well-documented parameters and an output schema, this description is complete enough for selecting and invoking the tool. It covers scope, ordering, item content, filtering behaviors, and a real workflow in several lines, so an agent can confidently decide when and how to call it correctly.

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% and each parameter already has a clear description covering time range, status enum semantics, quiz, respondent, pagination, and sort. The tool description reinforces the filtering categories but does not add meaningful parameter-level details beyond what the schema already explains, so baseline 3 is appropriate.

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 starts with a specific verb, 'List', and a concrete resource: '1:1 bookings (discovery calls / consultations booked from a quiz report page) of the current team'. It clearly distinguishes this from sibling tools like get_booking_availability, reschedule_booking, and update_booking_status by stating exactly what resource and scope this operation is about.

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?

It gives clear usage context: read-only listing of the current team's 1:1 bookings, earliest first, with defined filters and a typical use case ('status pending lists the approval queue waiting on someone'). It does not explicitly name alternative sibling tools or say when not to use this tool, so it is slightly short of fully explicit routing guidance.

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