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

Annotations already cover the safety profile (readOnly, non-destructive, openWorld), and the description adds non-obvious behavior: waitlisted customers lack a booking_id, which directly affects which downstream calls are valid, plus the auth prerequisite (Cotlet API key with access to this app). It does not discuss pagination or ordering of results.

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 core purpose and appropriately short for a single-parameter read tool. Minor redundancy: the first two sentences both restate that booked customers and the waitlist are returned, which could be merged.

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?

No output schema exists, and the description does a good job describing the return shape (bookings with booking_id and check-in status; waitlist entries without booking_id) plus the auth requirement. Details like pagination or result ordering are the only omissions for a one-param read 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?

Schema coverage is 100% and class_id is fully documented in-schema as the Class (session) ID from list_classes. The description only says the roster is 'for one class', adding no syntax or format detail beyond the schema, so the baseline 3 is appropriate.

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?

Names the specific resource (class roster), the verb (get), and the scope (one class), and precisely splits the two result groups: booked customers vs. waitlist, each with check-in status. An agent can tell this apart from sibling tools like momence_list_classes or momence_get_customer 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?

Gives clear usage context by tying the output to downstream actions: the booking_id is for check_in_customer and cancel_booking, while waitlisted customers cannot be checked in. It stops short of naming explicit alternatives or when-not-to-use conditions, so it is clear context without exclusions.

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