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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false). The description adds substantive behavioral context beyond that: the meaning of waitlist/standby membership ('waitlisted customers are not on the class until Mariana Tek auto-fills a freed spot or staff add them'), the Pick-A-Spot caveat, and an auth requirement. No pagination or volume notes, so not a 5.

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?

It is front-loaded with the return contents and each sentence carries information (roster contents, waitlist semantics, downstream use, auth). However the first sentence ('Reservations in a class with spot, payment used and status, plus the waitlist and standby list') largely restates the second, creating mild redundancy.

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, so the description carries the full burden of explaining return values, and it does so thoroughly: reservation items, the spot field with its Pick-A-Spot qualifier, payment and status, and the two secondary lists. Combined with the auth note, an agent has everything needed to call and interpret it.

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?

Only one parameter (class_id) with 100% schema coverage, so the schema already documents it fully and names its source (list_classes). The description adds no syntax or format detail beyond that, so the baseline 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?

The description states a specific verb and resource ('Returns the roster of one class') and enumerates exactly what comes back: reservations with spot, payment used and status, plus waitlist and standby lists. It is clearly distinguishable from list_classes (which enumerates classes) and list_customer_reservations (which enumerates a customer's bookings).

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 a concrete downstream use case ('Use reservation_id from each item to check in or cancel'), which tells the agent why this roster is fetched. It also names a prerequisite (Cotlet API key with access to this app). It stops short of explicitly stating when to prefer this over siblings like list_customer_reservations, so not a full 5.

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