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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavioral detail on top: ordering (soonest first), the two possible status values, that only confirmed bookings carry calendar links, how recurring occurrences are marked, and a prompt-injection warning about `untrusted` text. That last point is a genuine safety instruction not available anywhere in the structured fields.

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?

Front-loaded with the scope and ordering, then field semantics, then the untrusted-data warning — every sentence carries information. It is a dense single block that packs several distinct topics (status, links, recurrence, injection safety), so light structural separation would help, but nothing is padded.

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 carries the burden of explaining return shape, and it does: status values, calendar links, isRecurring/recurringGroupId, and the `untrusted` key convention. Combined with annotations covering safety, an agent has everything needed to call and interpret this tool.

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?

There is a single parameter and schema description coverage is 100%; the schema already explains that workspaceId comes from list_my_workspaces and is optional only for single-workspace users. The description adds nothing about the parameter, so the baseline of 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?

States a specific verb and resource with explicit scope: 'Your upcoming and in-progress reservations (not yet ended), soonest first', and pins down that it covers both confirmed bookings and pending booking requests. That scope statement is enough for an agent to tell it apart from list_booking_requests and list_rooms without opening a schema.

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 personal, time-bounded scope ('your', 'not yet ended'), so an agent can infer this is the personal itinerary view. However, there is no explicit when-to-use/when-not guidance and no sibling is named as an alternative (e.g. list_booking_requests for incoming requests to decide).

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