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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description stays consistent while adding behavior annotations don't cover: the email fallback sends a magic link on locktrip.com and returns `magicLinkSent: true`, with nothing shown or changed in the chat. It also documents default filtering (UPCOMING) and paging behavior.

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 purpose and filter semantics, then constraints, then return shape, then next-step routing — a logical order with no filler. It runs as one dense block, which is slightly heavy but every clause carries operational information.

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?

There is no output schema, and the description compensates by enumerating the returned `bookings[]` fields, `totalCount`, and the conditional price fields. Combined with the auth prerequisites and paging rules, an agent has everything needed to call it and interpret the result.

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 100%, so the baseline is 3, but the description adds meaning the schema does not: `type` defaults to UPCOMING, omitting `page` and `size` returns the full list, and `email` is only needed when no session exists. The sessionToken parameter's role is only lightly covered (schema notes it comes from `guest_login`).

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?

Opens with a specific verb and resource ("Lists the authenticated user's existing bookings") and immediately scopes it by the `type` filter values. It also names the sibling tools to use downstream (`get_booking_details`, `cancel_booking`), so an agent can separate listing from detail lookup or mutation.

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?

Explicitly states the precondition (registered LockTrip account session) and the exclusion (guest sessions from `guest_login` cannot list bookings), then gives the alternative path: pass `email` to trigger a sign-in link. It also routes the agent onward by telling it to pass a `bookingId` to `get_booking_details` or `cancel_booking`.

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