get_upcoming_bookings

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

Annotations already declare the safe-read profile (readOnly, idempotent, non-destructive), yet the description adds substantial context: time-zone assumptions, the booked/waitlisted/unknown state model, unbounded coverage horizon, untrusted external source names, and the guarantee that a failed lookup returns an error rather than an empty view. The error and trust disclosures are exactly the kind of behavioral detail an agent cannot get from 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?

Six sentences, each carrying a distinct semantic payload (scope, time zone, states, coverage limits, trust, failure mode), with purpose front-loaded. The density is high but no sentence is redundant, though the phrasing is slightly compressed for readability.

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 zero-parameter read tool with an output schema and full annotations, the description covers the remaining gaps an agent needs: what counts as a booking, the absence of a date horizon, content trust, and error semantics. Nothing required to call and interpret it correctly appears to be missing.

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?

The tool has zero parameters, which sets the baseline at 4 per the rubric. Coverage is inherent in the schema, and the description's note that the gym time zone is reported (and possibly assumed) clarifies how the implicit context affects results without introducing phantom inputs.

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 first sentence gives a specific verb and resource: "Read the account holder's upcoming booking view at a verified gym," which is concrete enough to distinguish this list tool from mutation siblings like prepare_booking_creation. It never names a sibling it is not, so the differentiation from get_booking_history or get_class_sessions must be inferred from the word "upcoming."

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 description gives interpretation rules (absence of a booking cannot prove no booking on an arbitrary date, reservations do not establish attendance) that help an agent use the result correctly. However, it never states when to choose this tool over get_booking_history or get_class_sessions, so routing guidance is only implied.

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