get_upcoming_bookings

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

The description substantially enriches the annotations: it explains time-zone assumptions, state distinctions, that reservations do not establish attendance, that coverage has no verified date horizon, that source names are untrusted, and that failures return errors rather than empty views. These details go far beyond readOnlyHint and openWorldHint 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?

Each sentence earns its place: the action is front-loaded, and the following sentences cover time-zone handling, state semantics, coverage limits, trust boundaries, and error behavior. The description is dense but not bloated, and every clause addresses a decision or interpretation an agent would otherwise lack.

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?

Given the output schema exists and the annotations already cover read-only, idempotent, and open-world behavior, the description completes the remaining picture: how to interpret states, what absence means, how time zones are handled, and what failure looks like. Nothing critical is missing for correct invocation and interpretation.

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?

Although schema description coverage is 0%, the description adds meaningful context for the single gymId parameter: the gym must be verified, and its reported time zone may be assumed. This is useful beyond the schema's pattern constraint, even though it does not explicitly name the parameter.

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 a specific verb and resource: "Read the account holder’s upcoming booking view at a verified gym." The word "upcoming" clearly distinguishes this from siblings like get_booking_history and get_class_sessions, so an agent can infer its scope even without opening the 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?

The tool's intended use is clearly implied: use it to read the account holder's upcoming booking view, including distinguishing booked, waitlisted, and unknown states. It does not explicitly name alternatives or exclusion conditions, but the scope is precise enough that an agent can select it appropriately among the listed siblings.

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